text:
Network File System Version 4 Working Group R. Thurlow Internet-Draft Sun Microsystems Intended status: Draft Standard Obsoletes: 1831 Expires:
December 12, 2008 June 10,April 30, 2009 October 30, 2008 RPC: Remote Procedure Call Protocol Specification Version 2 draft-ietf-nfsv4-rfc1831bis-09.txtdraft-ietf-nfsv4-rfc1831bis-10.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Discussion and suggestions for improvement are requested. This document will expire in December, 2008.April, 2009. Distribution of this draft is unlimited. Abstract This document describes the ONC (Open Network Computing) Remote Procedure Call (ONC RPC Version 2) protocol as it is currently deployed and accepted. It is meant to supersedeThis document obsoletes [RFC1831]. Requirements Language 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 [RFC2119]. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1 2. Changes since RFC 1831 . . . . . . . . . . . . . . . . . . . 1 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 1 4. The RPC Model . . . . . . . . . . . . . . . . . . . . . . . 1 5. Transports and Semantics . . . . . . . . . . . . . . . . . . 1 6. Binding and Rendezvous Independence . . . . . . . . . . . . 1 7. Authentication . . . . . . . . . . . . . . . . . . . . . . . 1 8. RPC Protocol Requirements . . . . . . . . . . . . . . . . . 1 8.1. RPC Programs and Procedures . . . . . . . . . . . . . . . 1 8.2. Authentication, Integrity and Privacy . . . . . . . . . . 1 8.3. Program Number Assignment . . . . . . . . . . . . . . . . 1 8.4. Other Uses of the RPC Protocol . . . . . . . . . . . . . . 1 8.4.1. Batching . . . . . . . . . . . . . . . . . . . . . . . . 1 8.4.2. Broadcast Remote Procedure Calls . . . . . . . . . . . . 1 9. The RPC Message Protocol . . . . . . . . . . . . . . . . . . 1 10. Authentication Protocols . . . . . . . . . . . . . . . . . 1 10.1. Null Authentication . . . . . . . . . . . . . . . . . . . 1 11. Record Marking Standard . . . . . . . . . . . . . . . . . . 1 12. The RPC Language . . . . . . . . . . . . . . . . . . . . . 1 12.1. An Example Service Described in the RPC Language . . . . 1 12.2. The RPC Language Specification . . . . . . . . . . . . . 1 12.3. Syntax Notes . . . . . . . . . . . . . . . . . . . . . . 1 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . 1 13.1. Numbering Requests to IANA . . . . . . . . . . . . . . . 1 13.2. Protecting Past Assignments . . . . . . . . . . . . . . . 1 13.3. RPC Number Assignment . . . . . . . . . . . . . . . . . . 1 13.3.1. To be assigned by IANA . . . . . . . . . . . . . . . . 1 13.3.2. Defined by local administrator . . . . . . . . . . . . 1 13.3.3. Transient block . . . . . . . . . . . . . . . . . . . . 1 13.3.4. Reserved block . . . . . . . . . . . . . . . . . . . . 1 13.3.5. RPC Number Sub-Blocks . . . . . . . . . . . . . . . . . 1 13.4. RPC Authentication Flavor Number Assignment . . . . . . . 1 13.4.1. Assignment Policy . . . . . . . . . . . . . . . . . . . 1 13.4.2. Auth Flavors vs. Pseudo-flavors . . . . . . . . . . . . 1 14. Security Considerations . . . . . . . . . . . . . . . . . . 1 15. Appendix A: System Authentication . . . . . . . . . . . . . 1 16. Appendix B: Requesting RPC program or authentication numbers . . . . . . . . . . . . . . . . . . . . . . . . . . 1 17. Full Copyright Statement . . . . . . . . . . . . . . . . . 1 18. Intellectual property . . . . . . . . . . . . . . . . . . . 1 19. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . 1 20. Normative References . . . . . . . . . . . . . . . . . . . 1 21. Informative References . . . . . . . . . . . . . . . . . . 1 22. Author's Address . . . . . . . . . . . . . . . . . . . . . 1 1. Introduction This document specifies version two of the message protocol used in ONC Remote Procedure Call (RPC). The message protocol is specified with the eXternal Data Representation (XDR) language [RFC4506]. This document assumes that the reader is familiar with XDR. It does not attempt to justify remote procedure calls systems or describe their use. The paper by Birrell and Nelson [XRPC] is recommended as an excellent background for the remote procedure call concept. 2. Changes since RFC 1831 This document is intended to replaceobsoletes RFC 1831 as the authoritative document describing RPC, without introducing any over-the-wire protocol changes. The main changes from RFC 1831 are: o Addition of an Appendix which describes how an implementor can request new RPC program numbers and authentication flavor numbers from IANA, rather than from Sun Microsystems o Addition of an "IANA Considerations" section which describes past program and authentication flavor number assignment policy and how IANA is intended to assign them in future o Clarification of the RPC Language Specification to match current usage o Enhancement of the "Security Considerations" section to reflect experience with strong security flavors o Specification of new authentication errors that are in common use in modern RPC implementations o Updates for the latest IETF intellectual property statements 3. Terminology This document discusses clients, calls, servers, replies, services, programs, procedures, and versions. Each remote procedure call has two sides: an active client side that makes the call to a server, which sends back a reply. A network service is a collection of one or more remote programs. A remote program implements one or more remote procedures; the procedures, their parameters, and results are documented in the specific program's protocol specification. A server may support more than one version of a remote program in order to be compatible with changing protocols. For example, a network file service may be composed of two programs. One program may deal with high-level applications such as file system access control and locking. The other may deal with low-level file input and output and have procedures like "read" and "write". A client of the network file service would call the procedures associated with the two programs of the service on behalf of the client. The terms client and server only apply to a particular transaction; a particular hardware entity (host) or software entity (process or program) could operate in both roles at different times. For example, a program that supplies remote execution service could also be a client of a network file service. 4. The RPC Model The ONC RPC protocol is based on the remote procedure call model, which is similar to the local procedure call model. In the local case, the caller places arguments to a procedure in some well- specified location (such as a register window). It then transfers control to the procedure, and eventually regains control. At that point, the results of the procedure are extracted from the well- specified location, and the caller continues execution. The remote procedure call model is similar. One thread of control logically winds through two processes: the caller's process, and a server's process. The caller process first sends a call message to the server process and waits (blocks) for a reply message. The call message includes the procedure's parameters, and the reply message includes the procedure's results. Once the reply message is received, the results of the procedure are extracted, and caller's execution is resumed. On the server side, a process is dormant awaiting the arrival of a call message. When one arrives, the server process extracts the procedure's parameters, computes the results, sends a reply message, and then awaits the next call message. In this model, only one of the two processes is active at any given time. However, this model is only given as an example. The ONC RPC protocol makes no restrictions on the concurrency model implemented, and others are possible. For example, an implementation may choose to have RPC calls be asynchronous, so that the client may do useful work while waiting for the reply from the server. Another possibility is to have the server create a separate task to process an incoming call, so that the original server can be free to receive other requests. There are a few important ways in which remote procedure calls differ from local procedure calls: o Error handling: failures of the remote server or network must be handled when using remote procedure calls. o Global variables and side-effects: since the server does not have access to the client's address space, hidden arguments cannot be passed as global variables or returned as side effects. o Performance: remote procedures usually operate one or more orders of magnitude slower than local procedure calls. o Authentication: since remote procedure calls can be transported over unsecured networks, authentication may be necessary. Authentication prevents one entity from masquerading as some other entity. The conclusion is that even though there are tools to automatically generate client and server libraries for a given service, protocols must still be designed carefully. 5. Transports and Semantics The RPC protocol can be implemented on several different transport protocols. The scope of the definition of the RPC protocol excludes how a message is passed from one process to another, and includes only the specification and interpretation of messages. However, the application may wish to obtain information about (and perhaps control over) the transport layer through an interface not specified in this document. For example, the transport protocol may impose a restriction on the maximum size of RPC messages, or it may be stream-oriented like TCP [RFC793] with no size limit. The client and server must agree on their transport protocol choices. It is important to point out that RPC does not try to implement any kind of reliability and that the application may need to be aware of the type of transport protocol underneath RPC. If it knows it is running on top of a reliable transport such as TCP, then most of the work is already done for it. On the other hand, if it is running on top of an unreliable transport such as UDP [RFC768], it must implement its own time-out, retransmission, and duplicate detection policies as the RPC protocol does not provide these services. Because of transport independence, the RPC protocol does not attach specific semantics to the remote procedures or their execution requirements. Semantics can be inferred from (but should be explicitly specified by) the underlying transport protocol. For example, consider RPC running on top of an unreliable transport such as UDP. If an application retransmits RPC call messages after time- outs, and does not receive a reply, it cannot infer anything about the number of times the procedure was executed. If it does receive a reply, then it can infer that the procedure was executed at least once. A server may wish to remember previously granted requests from a client and not regrant them in order to insure some degree of execute-at-most-once semantics. A server can do this by taking advantage of the transaction ID that is packaged with every RPC message. The main use of this transaction ID is by the client RPC entity in matching replies to calls. However, a client application may choose to reuse its previous transaction ID when retransmitting a call. The server may choose to remember this ID after executing a call and not execute calls with the same ID in order to achieve some degree of execute-at-most-once semantics. The server is not allowed to examine this ID in any other way except as a test for equality. On the other hand, if using a "reliable" transport such as TCP, the application can infer from a reply message that the procedure was executed exactly once, but if it receives no reply message, it cannot assume that the remote procedure was not executed. Note that even if a connection-oriented protocol like TCP is used, an application still needs time-outs and reconnection to handle server crashes. There are other possibilities for transports besides datagram- or connection-oriented protocols. For example, a request-reply protocol such as [VMTP] is perhaps a natural transport for RPC. ONC RPC currently uses both TCP and UDP transport protocols. Section 10 (Record Marking Standard) describes the mechanism employed by ONC RPC to utilize a connection-oriented, stream-oriented transport such as TCP. The mechanism by which future transports having different structural characteristics should be used to transfer ONC RPC messages should be specified by means of a standards-track RFC, once such additional transports are defined. 6. Binding and Rendezvous Independence The act of binding a particular client to a particular service and transport parameters is NOT part of this RPC protocol specification. This important and necessary function is left up to some higher-level software. Implementors could think of the RPC protocol as the jump-subroutine instruction ("JSR") of a network; the loader (binder) makes JSR useful, and the loader itself uses JSR to accomplish its task. Likewise, the binding software makes RPC useful, possibly using RPC to accomplish this task. 7. Authentication The RPC protocol provides the fields necessary for a client to identify itself to a service, and vice-versa, in each call and reply message. Security and access control mechanisms can be built on top of this message authentication. Several different authentication protocols can be supported. A field in the RPC header indicates which protocol is being used. More information on specific authentication protocols is in section 8.2: "Authentication, Integrity and Privacy". 8. RPC Protocol Requirements The RPC protocol must provide for the following: o Unique specification of a procedure to be called. o Provisions for matching response messages to request messages. o Provisions for authenticating the caller to service and vice- versa. Besides these requirements, features that detect the following are worth supporting because of protocol roll-over errors, implementation bugs, user error, and network administration: o RPC protocol mismatches. o Remote program protocol version mismatches. o Protocol errors (such as misspecification of a procedure's parameters). o Reasons why remote authentication failed. o Any other reasons why the desired procedure was not called. 8.1. RPC Programs and Procedures The RPC call message has three unsigned integer fields -- remote program number, remote program version number, and remote procedure number -- which uniquely identify the procedure to be called. Program numbers are administered by a central authority (IANA). Once implementors have a program number, they can implement their remote program; the first implementation would most likely have the version number 1 but MUST NOT be the number zero. Because most new protocols evolve, a version field of the call message identifies which version of the protocol the caller is using. Version numbers enable support of both old and new protocols through the same server process. The procedure number identifies the procedure to be called. These numbers are documented in the specific program's protocol specification. For example, a file service's protocol specification may state that its procedure number 5 is "read" and procedure number 12 is "write". Just as remote program protocols may change over several versions, the actual RPC message protocol could also change. Therefore, the call message also has in it the RPC version number, which is always equal to two for the version of RPC described here. The reply message to a request message has enough information to distinguish the following error conditions: o The remote implementation of RPC does not support protocol version 2. The lowest and highest supported RPC version numbers are returned. o The remote program is not available on the remote system. o The remote program does not support the requested version number. The lowest and highest supported remote program version numbers are returned. o The requested procedure number does not exist. (This is usually a client side protocol or programming error.) o The parameters to the remote procedure appear to be garbage from the server's point of view. (Again, this is usually caused by a disagreement about the protocol between client and service.) 8.2. Authentication, Integrity and Privacy Provisions for authentication of caller to service and vice-versa are provided as a part of the RPC protocol. The call message has two authentication fields, the credential and verifier. The reply message has one authentication field, the response verifier. The RPC protocol specification defines all three fields to be the following opaque type (in the eXternal Data Representation (XDR) language [RFC4506]): enum auth_flavor { AUTH_NONE = 0, AUTH_SYS = 1, AUTH_SHORT = 2, AUTH_DH = 3, RPCSEC_GSS = 6 /* and more to be defined */ }; struct opaque_auth { auth_flavor flavor; opaque body<400>; }; In other words, any "opaque_auth" structure is an "auth_flavor" enumeration followed by up to 400 bytes which are opaque to (uninterpreted by) the RPC protocol implementation. The interpretation and semantics of the data contained within the authentication fields is specified by individual, independent authentication protocol specifications. If authentication parameters were rejected, the reply message contains information stating why they were rejected. As demonstrated by RPCSEC_GSS, it is possible for an "auth_flavor" to also support integrity and privacy. 8.3. Program Number Assignment Program numbers are given out in groups of hexadecimal 20000000 (decimal 536870912) according to the following chart: 0x00000000 Reserved 0x00000001 - 0x1fffffff To be assigned by IANA 0x20000000 - 0x3fffffff Defined by local administrator (some blocks assigned here) 0x40000000 - 0x5fffffff Transient 0x60000000 - 0x7effffff Reserved 0x7f000000 - 0x7fffffff Assignment outstanding 0x80000000 - 0xffffffff Reserved The first group is a range of numbers administered by IANA and should be identical for all sites. The second range is for applications peculiar to a particular site. This range is intended primarily for debugging new programs. When a site develops an application that might be of general interest, that application should be given an assigned number in the first range. Application developers may apply for blocks of RPC program numbers in the first range by methods described in Appendix B. The third group is for applications that generate program numbers dynamically. The final groups are reserved for future use, and should not be used. 8.4. Other Uses of the RPC Protocol The intended use of this protocol is for calling remote procedures. Normally, each call message is matched with a reply message. However, the protocol itself is a message-passing protocol with which other (non-procedure call) protocols can be implemented. 8.4.1. Batching Batching is useful when a client wishes to send an arbitrarily large sequence of call messages to a server. Batching typically uses reliable byte stream protocols (like TCP) for its transport. In the case of batching, the client never waits for a reply from the server, and the server does not send replies to batch calls. A sequence of batch calls is usually terminated by a legitimate remote procedure call operation in order to flush the pipeline and get positive acknowledgement. 8.4.2. Broadcast Remote Procedure Calls In broadcast protocols, the client sends a broadcast call to the network and waits for numerous replies. This requires the use of packet-based protocols (like UDP) as its transport protocol. Servers that support broadcast protocols usually respond only when the call is successfully processed and are silent in the face of errors, but this varies with the application. The principles of broadcast RPC also apply to multicasting - an RPC request can be sent to a multicast address. 9. The RPC Message Protocol This section defines the RPC message protocol in the XDR data description language [RFC4506]. enum msg_type { CALL = 0, REPLY = 1 }; A reply to a call message can take on two forms: The message was either accepted or rejected. enum reply_stat { MSG_ACCEPTED = 0, MSG_DENIED = 1 }; Given that a call message was accepted, the following is the status of an attempt to call a remote procedure. enum accept_stat { SUCCESS = 0, /* RPC executed successfully */ PROG_UNAVAIL = 1, /* remote hasn't exported program */ PROG_MISMATCH = 2, /* remote can't support version # */ PROC_UNAVAIL = 3, /* program can't support procedure */ GARBAGE_ARGS = 4, /* procedure can't decode params */ SYSTEM_ERR = 5 /* e.g. memory allocation failure */ }; Reasons why a call message was rejected: enum reject_stat { RPC_MISMATCH = 0, /* RPC version number != 2 */ AUTH_ERROR = 1 /* remote can't authenticate caller */ }; Why authentication failed: enum auth_stat { AUTH_OK = 0, /* success */ /* * failed at remote end */ AUTH_BADCRED = 1, /* bad credential (seal broken) */ AUTH_REJECTEDCRED = 2, /* client must begin new session */ AUTH_BADVERF = 3, /* bad verifier (seal broken) */ AUTH_REJECTEDVERF = 4, /* verifier expired or replayed */ AUTH_TOOWEAK = 5, /* rejected for security reasons */ /* * failed locally */ AUTH_INVALIDRESP = 6, /* bogus response verifier */ AUTH_FAILED = 7, /* reason unknown */ /* * AUTH_KERB errors; deprecated. See [RFC2695] */ AUTH_KERB_GENERIC = 8, /* kerberos generic error */ AUTH_TIMEEXPIRE = 9, /* time of credential expired */ AUTH_TKT_FILE = 10, /* problem with ticket file */ AUTH_DECODE = 11, /* can't decode authenticator */ AUTH_NET_ADDR = 12, /* wrong net address in ticket */ /* * RPCSEC_GSS GSS related errors */ RPCSEC_GSS_NOCRED = 13, /* no credentials for user */ RPCSEC_GSS_FAILED = 14 /* GSS failure, creds deleted */ }; The RPC message: All messages start with a transaction identifier, xid, followed by a two-armed discriminated union. The union's discriminant is a msg_type which switches to one of the two types of the message. The xid of a REPLY message always matches that of the initiating CALL message. NB: The xid field is only used for clients matching reply messages with call messages or for servers detecting retransmissions; the service side cannot treat this id as any type of sequence number. struct rpc_msg { unsigned int xid; union switch (msg_type mtype) { case CALL: call_body cbody; case REPLY: reply_body rbody; } body; }; Body of an RPC call: In version 2 of the RPC protocol specification, rpcvers MUST be equal to 2. The fields prog, vers, and proc specify the remote program, its version number, and the procedure within the remote program to be called. After these fields are two authentication parameters: cred (authentication credential) and verf (authentication verifier). The two authentication parameters are followed by the parameters to the remote procedure, which are specified by the specific program protocol. The purpose of the authentication verifier is to validate the authentication credential. Note that these two items are historically separate, but are always used together as one logical entity. struct call_body { unsigned int rpcvers; /* must be equal to two (2) */ unsigned int prog; unsigned int vers; unsigned int proc; opaque_auth cred; opaque_auth verf; /* procedure specific parameters start here */ }; Body of a reply to an RPC call: union reply_body switch (reply_stat stat) { case MSG_ACCEPTED: accepted_reply areply; case MSG_DENIED: rejected_reply rreply; } reply; Reply to an RPC call that was accepted by the server: There could be an error even though the call was accepted. The first field is an authentication verifier that the server generates in order to validate itself to the client. It is followed by a union whose discriminant is an enum accept_stat. The SUCCESS arm of the union is protocol specific. The PROG_UNAVAIL, PROC_UNAVAIL, GARBAGE_ARGS, and SYSTEM_ERR arms of the union are void. The PROG_MISMATCH arm specifies the lowest and highest version numbers of the remote program supported by the server. struct accepted_reply { opaque_auth verf; union switch (accept_stat stat) { case SUCCESS: opaque results[0]; /* * procedure-specific results start here */ case PROG_MISMATCH: struct { unsigned int low; unsigned int high; } mismatch_info; default: /* * Void. Cases include PROG_UNAVAIL, PROC_UNAVAIL, * GARBAGE_ARGS, and SYSTEM_ERR. */ void; } reply_data; }; Reply to an RPC call that was rejected by the server: The call can be rejected for two reasons: either the server is not running a compatible version of the RPC protocol (RPC_MISMATCH), or the server rejects the identity of the caller (AUTH_ERROR). In case of an RPC version mismatch, the server returns the lowest and highest supported RPC version numbers. In case of invalid authentication, failure status is returned. union rejected_reply switch (reject_stat stat) { case RPC_MISMATCH: struct { unsigned int low; unsigned int high; } mismatch_info; case AUTH_ERROR: auth_stat stat; }; 10. Authentication Protocols As previously stated, authentication parameters are opaque, but open-ended to the rest of the RPC protocol. This section defines two standard "flavors" of authentication. Implementors are free to invent new authentication types, with the same rules of flavor number assignment as there is for program number assignment. The "flavor" of a credential or verifier refers to the value of the "flavor" field in the opaque_auth structure. Flavor numbers, like RPC program numbers, are also administered centrally, and developers may assign new flavor numbers by methods described in Appendix B. Credentials and verifiers are represented as variable length opaque data (the "body" field in the opaque_auth structure). In this document, two flavors of authentication are described. Of these, Null authentication (described in the next subsection) is mandatory - it MUST be available in all implementations. System authentication (AUTH_SYS) is described in Appendix A. Implementors MAY include AUTH_SYS in their implementations to support existing applications. See "Security Considerations" for information about other, more secure, authentication flavors. 10.1. Null Authentication Often calls must be made where the client does not care about its identity or the server does not care who the client is. In this case, the flavor of the RPC message's credential, verifier, and reply verifier is "AUTH_NONE". Opaque data associated with "AUTH_NONE" is undefined. It is recommended that the length of the opaque data be zero. 11. Record Marking Standard When RPC messages are passed on top of a byte stream transport protocol (like TCP), it is necessary to delimit one message from another in order to detect and possibly recover from protocol errors. This is called record marking (RM). One RPC message fits into one RM record. A record is composed of one or more record fragments. A record fragment is a four-byte header followed by 0 to (2**31) - 1 bytes of fragment data. The bytes encode an unsigned binary number; as with XDR integers, the byte order is from highest to lowest. The number encodes two values -- a boolean which indicates whether the fragment is the last fragment of the record (bit value 1 implies the fragment is the last fragment) and a 31-bit unsigned binary value which is the length in bytes of the fragment's data. The boolean value is the highest-order bit of the header; the length is the 31 low-order bits. (Note that this record specification is NOT in XDR standard form!) 12. The RPC Language Just as there was a need to describe the XDR data-types in a formal language, there is also need to describe the procedures that operate on these XDR data-types in a formal language as well. The RPC Language is an extension to the XDR language, with the addition of "program", "procedure", and "version" declarations. The keywords "program" and "version" are reserved in the RPC Language, and implementations of XDR compilers MAY reserve these keywords even when provided pure XDR, non-RPC, descriptions. The following example is used to describe the essence of the language. 12.1. An Example Service Described in the RPC Language Here is an example of the specification of a simple ping program. program PING_PROG { /* * Latest and greatest version */ version PING_VERS_PINGBACK { void PINGPROC_NULL(void) = 0; /* * Ping the client, return the round-trip time * (in microseconds). Returns -1 if the operation * timed out. */ int PINGPROC_PINGBACK(void) = 1; } = 2; /* * Original version */ version PING_VERS_ORIG { void PINGPROC_NULL(void) = 0; } = 1; } = 1; const PING_VERS = 2; /* latest version */ The first version described is PING_VERS_PINGBACK with two procedures, PINGPROC_NULL and PINGPROC_PINGBACK. PINGPROC_NULL takes no arguments and returns no results, but it is useful for computing round-trip times from the client to the server and back again. By convention, procedure 0 of any RPC protocol should have the same semantics, and never require any kind of authentication. The second procedure is used for the client to have the server do a reverse ping operation back to the client, and it returns the amount of time (in microseconds) that the operation used. The next version, PING_VERS_ORIG, is the original version of the protocol and it does not contain PINGPROC_PINGBACK procedure. It is useful for compatibility with old client programs, and as this program matures it may be dropped from the protocol entirely. 12.2. The RPC Language Specification The RPC language is identical to the XDR language defined in RFC 4506, except for the added definition of a "program-def" described below. program-def: "program" identifier "{" version-def version-def * "}" "=" constant ";" version-def: "version" identifier "{" procedure-def procedure-def * "}" "=" constant ";" procedure-def: proc-return identifier "(" proc-firstarg ("," type-specifier )* ")" "=" constant ";" proc-return: "void" | type-specifier proc-firstarg: "void" | type-specifier 12.3. Syntax Notes o The following keywords are added and cannot be used as identifiers: "program" and "version"; o A version name cannot occur more than once within the scope of a program definition. Nor can a version number occur more than once within the scope of a program definition. o A procedure name cannot occur more than once within the scope of a version definition. Nor can a procedure number occur more than once within the scope of version definition. o Program identifiers are in the same name space as constant and type identifiers. o Only unsigned constants can be assigned to programs, versions and procedures. o Current RPC language compilers do not generally support more than one type-specifier in procedure argument lists; the usual practice is to wrap arguments into a structure. 13. IANA Considerations The assignment of RPC program numbers and authentication flavor numbers has in the past been performed by Sun Microsystems, Inc (Sun). This is inappropriate for an IETF standards-track protocol, as such work is done well by the Internet Assigned Numbers Authority (IANA). This document proposes the transfer of authority over RPC program numbers and authentication flavor numbers described here from Sun Microsystems, Inc. to IANA and proposes how IANA will maintain and assign RPC program numbers and authentication flavor numbers. Users of RPC protocols will benefit by having an independent body responsible for RPC number assignments. 13.1. Numbering Requests to IANA Appendix B of this document describes the information to be sent to IANA to request one or more RPC numbers and the rules that apply. IANA should review this part ofstore the document as well.request for documentary purposes, and put the following information into the public registry: o The short description of purpose and use o The program number(s) assigned o The short identifier string(s) 13.2. Protecting Past Assignments Sun has made assignments in both number spaces since the original deployment of RPC. The assignments made by Sun Microsystems are still valid, and will be preserved. Sun will communicate all current assignments in both number spaces to IANA before final handoff of number assignment is done. At the time of submission of this draft, current assignments were listed at: http://www.nfsv4-editor.org/rpc-numbers-1831bis.txt 13.3. RPC Number Assignment Future IANA practice should deal with the following partitioning of the 32-bit number space as listed in Section 8.3. Detailed information for the administration of the partitioned blocks in Section 8.3. is given below. 13.3.1. To be assigned by IANA The first block will be administered by IANA, with previous assignments by Sun protected. Previous assignments were restricted to the range decimal 100000-399999 (0x000186a0 to 0x00061a7f), therefore IANA should begin assignments at decimal 400000. Individual numbers should be grated on a first-come, first-served basis, and blocks should be granted under rules related to the size of the block. 13.3.2. Defined by local administrator The "Defined by local administrator" block is available for any local administrative domain to use, in a similar manner to IP address ranges reserved for private use. The expected use would be through the establishment of a local domain "authority" for assigning numbers from this range. This authority would establish any policies or procedures to be used within that local domain for use or assignment of RPC numbers from the range. The local domain should be sufficiently isolated that it would be unlikely that RPC applications developed by other local domains could communicate with the domain. This could result in RPC number contention, which would cause one of the applications to fail. In the absence of a local administrator, this block can be utilized in a "Private Use" manner per [RFC5226]. 13.3.3. Transient block The "Transient" block can be used by any RPC application on a "as available" basis. This range is intended for services that can communicate a dynamically selected RPC program number to clients of the service. Any mechanism can be used to communicate the number. Examples include shared memory when the client and server are located on the same system, or a network message (either RPC or otherwise) that disseminates the selected number. The transient block is not administered. An RPC service uses this range by selecting a number in the transient range and attempting to register that number with the local system's RPC bindery (see the RPCBPROC_SET or PMAPPROC_SET procedures in "Binding Protocols for ONC RPC", [RFC1833]). If successful, no other RPC service was using that number and the RPC Bindery has assigned that number to the requesting RPC application. The registration is valid until the RPC Bindery terminates, which normally would only happen if the system reboots causing all applications, including the RPC service using the transient number, to terminate. If the transient number registration fails, another RPC application is using the number and the requestor must select another number and try again. To avoid conflicts, the recommended method is to select a number randomly from the transient range. 13.3.4. Reserved block The "Reserved" blocks are available for future use. RPC applications must not use numbers in these ranges unless their use is allowed by future action by the IESG. 13.3.5. RPC Number Sub-Blocks RPC numbers are usually assigned for specific RPC services. Some applications, however, require multiple RPC numbers for a service. The most common example is an RPC service that needs to have multiple instances of the service active simultaneously at a specific site. RPC does not have an "instance identifier" in the protocol, so either a mechanism must be implemented to multiplex RPC requests amongst various instances of the service, or unique RPC numbers must be used by each instance. In these cases, the RPC protocol used with the various numbers may be different or the same. The numbers may be assigned dynamically by the application, or as part of a site-specific administrative decision. If possible, RPC services that dynamically assign RPC numbers should use the "Transient" RPC number block defined in section 2. If not possible, RPC number sub-blocks may be requested. Assignment of RPC Number Sub-Blocks is controlled by the size of the sub-block being requested. "Specification Required" and "IESG Approval" are used as defined by [RFC5226] Section 4.1. Size of sub-block Assignment Method Authority ----------------- ----------------- --------- Up to 100 numbers First Come First Served IANA Up to 1000 numbers Specification Required IANA More than 1000 numbers IESG Approval required IESG Note: sub-blocks can be any size. The limits given above are maximums and smaller size sub-blocks are allowed. Sub-blocks sized up to 100 numbers may be assigned by IANA on a First Come First Served basis. The RPC Service Description included in the range must include an indication of how the sub-block is managed. At minimum, the statement should indicate whether the sub-block is used with a single RPC protocol or multiple RPC protocols, and whether the numbers are dynamically assigned or statically (through administrative action) assigned. Sub-blocks of up to 1000 numbers must be documented in detail. The documentation must describe the RPC protocol or protocols that are to be used in the range. It must also describe how the numbers within the sub-block are to be assigned or used. Sub-blocks sized over 1000 numbers must be documented as described above, however an Internet Draftand the assignment must be submitted as an Informational or standards-track RFC. If accepted as either, IANA will assignapproved by the requested number sub-block.IESG. It is expected that this will be rare. In order to avoid multiple requests of large blocks of numbers the following rule is proposed. Requests up to and including 100 RPC numbers are handled via the First Come First Served assignment method. This 100 number threshhold applies to the total number of RPC numbers assigned to an individual or entity. For example, if an individual or entity first requests say 70 numbers, and then later requests 40 numbers, then the request for the 40 numbers will be assigned via the Specification Required method. As long as the total number of numbers assigned does not exceed 1000, IANA is free to waive the Specification Required assignment for incremental requests of less than 100 numbers. If an individual or entity has under 1000 numbers and later requests an additional set of numbers such that the individual or entity would be granted over 1000 numbers, then the individual or entity will have theadditional request submitted to the IESG. IESG is free to waive thewill require IESG Action Required assignment method for incremental requests of less than 1000 numbers.Approval. 13.4. RPC Authentication Flavor Number Assignment The second number space is the authentication mechanism identifier, or "flavor", number. This number is used to distinguish between various authentication mechanisms which can be optionally used with an RPC message. An authentication identifier is used in the "flavor" field of the "opaque_auth" structure. 13.4.1. Assignment Policy Appendix B of this document describes the information to be sent to IANA to request one or more RPC auth numbers and the rules that apply. IANA should store the request for documentary purposes, and put the following information into the public registry: o The short identifier string(s) o The auth number(s) assigned o The short description of purpose and use 13.4.2. Auth Flavors vs. Pseudo-flavors Recent progress in RPC security has moved away from new auth flavors as used by AUTH_DH [DH], and focused on using the existing RPCSEC_GSS [RFC2203] flavor and inventing novel GSS-API mechanisms which can be used with it. Even though RPCSEC_GSS is an assigned authentication flavor, use of a new RPCSEC_GSS mechanism with NFS ([RFC1094] [RFC1813] and [RFC3530]) will require the registration of 'pseudo- flavors' which are used to negotiate security mechanisms in an unambiguous way, as defined by [RFC2623]. Existing pseudo-flavors have been granted in the decimal range 390000-390255. New pseudo- flavor requests should be granted by IANA within this block on a First Come First Served basis. For non-pseudo-flavor requests, IANA should begin granting RPC authentication flavor numbers at 400000 on a First Come First Served basis to avoid conflicts with currently granted numbers. For authentication flavors or RPCSEC_GSS mechanisms to be used on the Internet, it is strongly advised that an informational or standards- track RFC be published describing the authentication mechanism behaviour and parameters. 14. Security Considerations AUTH_SYS as described in Appendix A is known to be insecure due to the lack of a verifier to permit the credential to be validated. AUTH_SYS SHOULD NOT be used for services which permit clients to modify data. AUTH_SYS MUST NOT be specified as RECOMMENDED or REQUIRED for any standards-track RPC service. [RFC2203] defines a new security flavor, RPCSEC_GSS, which permits GSS-API [RFC2743] mechanisms to be used for securing RPC. All non- trivial RPC programs developed in future should implement RPCSEC_GSS-based security appropriately. [RFC2623] describes how this was done for a widely deployed RPC program. 15. Appendix A: System Authentication The client may wish to identify itself, for example, as it is identified on a UNIX(tm) system. The flavor of the client credential is "AUTH_SYS". The opaque data constituting the credential encodes the following structure: struct authsys_parms { unsigned int stamp; string machinename<255>; unsigned int uid; unsigned int gid; unsigned int gids<16>; }; The "stamp" is an arbitrary ID which the caller machine may generate. The "machinename" is the name of the caller's machine (like "krypton"). The "uid" is the caller's effective user ID. The "gid" is the caller's effective group ID. The "gids" is a counted array of groups which contain the caller as a member. The verifier accompanying the credential should have "AUTH_NONE" flavor value (defined above). Note this credential is only unique within a particular domain of machine names, uids, and gids. The flavor value of the verifier received in the reply message from the server may be "AUTH_NONE" or "AUTH_SHORT". In the case of "AUTH_SHORT", the bytes of the reply verifier's string encode an opaque structure. This new opaque structure may now be passed to the server instead of the original "AUTH_SYS" flavor credential. The server may keep a cache which maps shorthand opaque structures (passed back by way of an "AUTH_SHORT" style reply verifier) to the original credentials of the caller. The caller can save network bandwidth and server cpu cycles by using the shorthand credential. The server may flush the shorthand opaque structure at any time. If this happens, the remote procedure call message will be rejected due to an authentication error. The reason for the failure will be "AUTH_REJECTEDCRED". At this point, the client may wish to try the original "AUTH_SYS" style of credential. It should be noted that use of this flavor of authentication does not guarantee any security for the users or providers of a service, in itself. The authentication provided by this scheme can be considered legitimate only when applications using this scheme and the network can be secured externally, and privileged transport addresses are used for the communicating end-points (an example of this is the use of privileged TCP/UDP ports in Unix systems - note that not all systems enforce privileged transport address mechanisms). 16. Appendix B: Requesting RPC program or authentication numbers RPC numbers which must be unique across all networks are assigned by the Internet Assigned Number Authority. To apply for a single number or a block of numbers, electronic mail must be sent to IANA <firstname.lastname@example.com> with the following information: o The type of number(s) (program number or authentication flavor number) sought o How many numbers are sought o The name of person or company which will use the number o An "identifier string" which associates the number with a service o Email address of the contact person for the service which will be using the number. o A short description of the purpose and use of the number o If an authentication flavor number is sought, and the number will be a 'pseudo-flavor' intended for use with RPCSEC_GSS and NFS, mappings analogous to those in Section 4.2 of [RFC2623] are required. Specific numbers cannot be requested. Numbers are assigned on a First Come First Served basis. For all RPC authentication flavor numbers to used on the Internet, it is strongly advised that an informational or standards-track RFC be published describing the authentication mechanism behaviour and parameters. 17. Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 18. Intellectual property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- firstname.lastname@example.com. 19. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). 20. Normative References [RFC4506] Eisler, M., "XDR: External Data Representation Standard", RFC 4506, 21. Informative References [XRPC] Birrell, A. D. & Nelson, B. J., "Implementing Remote Procedure Calls", XEROX CSL-83-7, October 1983. [VMTP] Cheriton, D., "VMTP: Versatile Message Transaction Protocol", Preliminary Version 0.3, Stanford University, January 1987. [DH] Diffie & Hellman, "New Directions in Cryptography", IEEE Transactions on Information Theory IT-22, November 1976. [RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC/Information Sciences Institute, August 1980. [RFC793] Postel, J., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", STD 7, RFC 793, USC/Information Sciences Institute, September 1981. [RFC1094] Sun Microsystems, Inc., "NFS: Network File System Protocol Specification", RFC 1094, March 1989. [RFC1813] Callaghan, B., Pawlowski, B., Staubach, P., "NFS Version 3 Protocol Specification", RFC 1813, June 1995. [RFC1831] R. Srinivasan, "RPC: Remote Procedure Call Protocol Specification Version 2", RFC 1831, August 1995. [RFC1833] R. Srinivasan, "Binding Protocols for ONC RPC Version 2", RFC 1833, August 1995. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2203] Eisler, M., Chiu, A., Ling, L., "RPCSEC_GSS Protocol Specification", RFC 2203, September 1997 [RFC2623] Eisler, M., "NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5", RFC 2623, June 1999. [RFC2695] Chiu, A., "Authentication Mechanisms for ONC RPC", RFC 2695, September 1999. [RFC2743] Linn. J., "Generic Security Service Application Program Interface Version 2, Update 1", RFC 2743, January 2000. [RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., Beame, C., Eisler, M., Noveck, D., "Network File System (NFS) version 4 Protocol", RFC 3530, April 2003. [RFC5226] Narten, T. and Alvestrand, H., "Guidelines for Writing an IANA Considerations Section in RFCs", RFC 5226, May 2008. 22. Author's Address Address comments related to this memorandum to: email@example.com Robert Thurlow Sun Microsystems, Inc. 500 Eldorado Boulevard, UBRM05-171 Broomfield, CO 80021 Phone: 877-718-3419 E-mail: firstname.lastname@example.com


text:
I love that New Westminster has so many festivals and events. There's been some news lately that a few festivals in New West have had to postpone, cancel, or reschedule. I personally think it is good for festivals to change things up and believe nothing is "sacred" in terms of dates or formats or even names. There really is something for everyone here, depending upon what interests you and your family the most. And, festival-goers evolve. My nearly eight year old loves certain events, but in six short years I can guarantee he won't really be as keen on the children's festival as he once was. I like that there are always things that are right for me, right at that moment. And with 67,000 of us, I think there's enough New Westers to support well organized and fun events. I am thankful for volunteers who put in lots of effort, whether or not their event is for me. They make the city better.
Sapperton Day is one of my favourite festivals in the City, and it's one my neighbours and I have been planning our block party around for the past four years now. Its broad appeal is part of why I like it so much as it is everything that's great about a small community festival – a closed street, something for all ages, inexpensive, lots of colours, sounds, and fun, and lots of things to check out. It is put together by volunteers, and raises much needed money for the Royal Columbian Hospital Foundation. Sapperton Day is not without its own re-invention – apparently it too, has gone on hiatus before. This year, the weather was delightful and Sapperton Day was a good time.
Many thanks to Paul Fuoco, who took all of these pictures at this year's fest back in June, and is letting me share my favourites. I admit I picked not one, but two dog pictures. These pictures really made me feel warm and fuzzy for my neighbourhood that they pull off such greatness. Thank you to the organizers!

subset: commoncrawl


text:
McAllen ISD students in the audio-visual program (known by the call letters KMAC) won multiple awards at the International Student Television Network Conference in late March in Nashville, Tenn. More than 3,500 students competed in more than 30 contests. KMAC students competed in 10 contests and placed in four of them.
"This was KMAC's 15th year attending the contest and it was also our best year yet with results," KMAC Instructor Rob Garza said. "Most contests had 60 teams or more competing."
The group of Kevin Cavazos (McAllen High), May Ramirez (McAllen High), John Rodriguez (McAllen Memorial High) and Karla Vargas (McAllen High) took first place in the Crazy 8's Short Film Contest.
For the Crazy 8 film, students are given eight hours to develop an idea, record and edit a film. They had to follow a prompt; in this case, it was "Stuck On Repeat."
"Our students decided to do a film on school violence," Garza said. "They played our first place entry after results were announced. When it finished playing, the auditorium of 3,000 plus students and teachers was completely silent. As our students came down from the stage from receiving the award, the entire auditorium stood up and began clapping, giving our students a standing ovation."
The first place award for Radio Host went to Sebastian Davila (Rowe High) and Selisa Gutierrez (Rowe).
KMAC's Music Video took second place. That team included John Rodriguez (Memorial), Michael Pequeno (Memorial), Kevin Cavazos (McAllen High), Carolina Suarez (McAllen High) and Ezra Landeros (McAllen High).
KMAC's Short Story team took second place. That team included Matt Mandes (Memorial), Acril Acosta (Rowe), Stephanie Rodriguez (Rowe), Sebastian Davila (Rowe) and Nico Hinojosa (McAllen High).


text:
PASSINGS: Milka Planinc, Jerrold Marsden, Gloria Green, Frank Bourgholtzer, Frederik Chel, Sherman J. Maisel
Milka Planinc
Former premier of Yugoslavia
Milka Planinc, 85, who was prime minister in the 1980s in what was then communist Yugoslavia, died Thursday in a Zagreb clinic after a long illness, the Croatian state-run news agency reported.
Planinc was a high-level communist official in Yugoslavia, a close associate of longtime President Josip Broz Tito and the first female premier of a communist country. From 1982 to 1986, she headed the Federal Executive Council, the federal Cabinet.
Yugoslavia disintegrated in wars in the early 1990s, and the country no longer exists. Planinc retired from politics.
Born Nov. 21, 1924, she was disliked in Croatia for crushing a 1971 movement seeking more independence for Croatia within Yugoslavia.
Jerrold Marsden
Caltech mathematician
Jerrold Marsden, 68, a Caltech professor who was one of the world's leading experts in mathematical and theoretical mechanics, died Sept. 21 at his home in Pasadena, the school announced. He had cancer.
Marsden was the Carl F. Braun professor of Engineering, Control and Dynamical Systems and Applied and Computational Mathematics. His research led to advances in such fields as spacecraft mission design.
Marsden went to Caltech in 1992 from the faculty at UC Berkeley.
He was born Aug. 17, 1942, in British Columbia and graduated from the University of Toronto in 1965 with a bachelor of science degree in mathematics. He earned a doctorate from Princeton University in 1968 in applied mathematics.
Marsden also helped found and until 1994 was director of the Fields Institute, a mathematical research facility at the University of Toronto.
Gloria Green
Glendale Career College owner
Gloria Green, 82, longtime owner of Glendale Career College, died Sept. 24 at the Rehabilitation Centre in Beverly Hills of complications from diabetes, said her son, Richard.
Glendale Career College offered career training to more than 35,000 people during Green's 25 years. She took over what had been the Glendale College of Business in 1975 and expanded the curriculum to include instruction in technology as well as medical and legal fields. She also ran the Nevada Career Institute in Las Vegas.
She was born Jan. 18, 1928, in Brooklyn, N.Y. Green sold the college in 2000 and worked as an actress, including a role in the 2006 film "Even Money."
Frank Bourgholtzer
NBC's first full-time White House reporter
Frank Bourgholtzer, 90, the first full-time White House correspondent for NBC News, died Friday at his home in Santa Monica, his family said.
Bourgholtzer, who was born in New York City on Oct. 26, 1919, joined NBC in 1946 and covered President Truman from 1947 to 1953. After assignments in Europe, he joined the NBC bureau in Los Angeles in 1969, where he remained until retiring in 1986.
Frederik Chel, who served in the state Assembly from 1974 to 1978, died Oct. 5 at his home in Long Beach of complications from Parkinson's disease, said his son, Fred. Chel was a Democrat representing the 58th District, which then included Lakewood, Hawaiian Gardens and part of Long Beach. He was 80.
Sherman J. Maisel, a former governor of the Federal Reserve and a professor emeritus at UC Berkeley's Haas School of Business, died Sept. 29 of respiratory failure in San Francisco, the school announced. He was 92.
-- Times staff and wire reports


text:
How would you feel if your smartphone is secretly generating profit for cybercriminals without your knowledge? These unsolicited activities are not only security and privacy risks, they can impact your smartphone's performance as well.
Researchers from eZanga used the company's Anura ad fraud protection software to detect ad click attempts from hundreds of Android apps that run hidden adware to generate fraudulent revenue.
Back in June, the researchers found 317 apps in the Google Play store that were created using a software development kit (SDK) that hides ad fraud code. Another 1,300 malicious apps were also found in third-party app stores.
The infected apps, which range from free live wallpaper apps to free camera apps, automatically run scripts in the background to mimic human clicks and generate page views, all without the user's permission.
This essentially turns an infected phone into an ad bot that's under its developer's beck and call.
eZanga said that these ad fraud apps could have garnered between 4.1 to 14.2 million installs so far. With these kinds of numbers, millions of Android phones may have been recruited to this army of ad fraud bots without their owner's knowledge.
The scheme was first uncovered in June when Anura isolated two dubious wallpaper apps named Lovely Rose and Oriental Beauty and tested them for questionable behavior. Within a 24-hour period, the tests of Android phones with these apps installed were found to request a total of 3,061 ads and 169 successful clicks, all this while the phones were in sleep mode.
These fake ad clicks and unsolicited activity can cost the industry a whopping $6.5 billion in lost advertising revenue.
The researchers also identified Google Play Store app developers who are releasing multiple apps displaying the same dubious characteristics.
Included in this list of developers are names like Attunable, Classywall, Firamo, FlameryHot, NeonApp, Goopolo, Litvinka Co, Livelypapir, Tuneatpa Personalization, Waterflo, X Soft, and Zheka.
Thankfully, most of the apps in were removed from the Google Play Store shortly after eZanga's research findings were released. However, about 6,000 more apps were still seen floating around third-party app stores tainted with a tweaked version of the ad fraud malware.
Is your Android phone secretly an ad bot?
Since ad fraud malware lurks in the background to do its shady deed, here are tell-tale signs that your phone may be infected.
First, check for data spikes. Adware infected phones usually perform unsolicited clicks in the background to generate profit for cybercriminals. All of these stealthy tactics use up bandwidth and the unauthorized data they consume should be fairly easy to spot.
Second, battery drain. As you can imagine, all this unauthorized background activity not only takes a toll on your data usage, it can impact your battery life, as well. Since your phone is still busy clicking ads to generate page views in the background even while it's idle, it can never be really at rest.
Aside from adware, there are different kinds of malware that can infect your Android phone. Click here to read more about ways on how to detect a virus on your Android phone.
How to protect yourself from ad fraud malware
You can't be too careful with apps nowadays. As you can see, your phone can be turned into a fraudulent ad revenue bot without your knowledge. Follow these basic tips to keep the cybercriminals at bay:
- Opt in to Google Play Protect – It is designed to work in the background, protecting users from malicious apps in real time. Click here to learn more about it and how to opt in.
- Only download apps from the Google Play Store – Even though some malicious apps make it into the Play Store, it does have a more thorough screening process. This cuts down on the chances a malicious app makes it in. Third-party app stores don't have these screening processes.
- Keep "unknown sources" disabled while not using it.
- Make sure your gadget is updated with the most recent Android security update.
- Check the app's developer – Verifying the name of the app developer is important. Copycat apps will have a different developer's name than the actual one. Before downloading an app, do a Google search to find the original developer.
- Reviews – Most of the popular apps will have reviews by other users in the app store. You can sometimes find reviews by experts online. These are helpful at pointing out malicious or faulty apps. If you find a review warning the app is malicious, do NOT download it.
More from Komando.com:
Common security risks every smartphone user should know about
Critical steps to secure your home Wi-Fi


text:
Apartments In North San AntonioIron Horse Valley offers an astounding amenities package with all of the perks and none of the hassle. Breathe a little easier with community conveniences like online payments, on-site maintenance, and package receiving. Our limited access gated community also provides a clothes care center that will save you from inconvenient trips to the laundromat. Take advantage of our variety of on-site sports courts offering spaces for tennis, volleyball, and basketball. Our northeast San Antonio community isn't just a great place to live, it is also a great place to entertain. Two sparkling pools and a rentable community clubroom will make it easy to host your next big gathering. We also welcome your furry friends! Contact our leasing office to learn more about our apartments in north San Antonio.
Community Amenities
- Online Payments Available
Free e-check option
Accepts credit card payments
Accepts cash payments via MoneyGram
- 2 Pools
- Basketball Court
- 3 On-site Laundry Facilities
- Club House
- On-Site Maintenance
- On-Site Management
- Public Transportation
- Tennis Court
- Volleyball Court
Apartment Amenities
Certain floor plans may have different amenities depending on when they were updated, what building they're in, etc. To tour our floor plans and see what amenities may be available, please call us at (210) 657-5001.
- Ceiling Fans
- Fire Places (select units)
- Oversized Closets
- Patio/Balcony
- Spacious Floorplans
- Washer/Dryer Connections


text:
Create an Account - Increase your productivity, customize your experience, and engage in information you care about.
If you have received a violation for expired registration, the citation can be dismissed only under these conditions:
Under no circumstances will any court personnel come out to your car and view the registration sticker as proof or renewal. A picture of your sticker on the window is not sufficient to obtain a dismissal of this type of violation.


text:
Scholar Sessions
Next week's SCHOLAR online sessions will be:
- Advanced Higher Modern Languages Tuesday 22nd March 7.00 pm
- Advanced Higher Computing Science Wednesday 23rd March 7.00pm
- National 5 Maths Thursday 24th March 6.00pm
Full details can be found on the SCHOLAR website.
Tutors will also be online to answer student questions on the discussion boards, details can be found here.
Please note that Modern Language and Computing Science homework sessions now start at 7pm and Ask a Tutor availability starts at 8pm.
More information about dates and times can be found here.


text:
Check out this cool embroidered patch of man's face with tophat, mustache and eyeglass. It is sewn with khaiki thread, dark brown thread is used for the tophat and the mustache and eye piece is sewn in black. This patch is 3" in diameter. It has an iron on adhesive to help with application on your garments or gear.
Check out some of my other patches as well that you may want to purchase along with this one.
International orders ship First Class.
This patch will ship 3-5 business days upon ordering.
USPS First Class Shipping.
Finished Patch/Badge can be applied directly to garment with heat-press, hand iron or sewn on.
If using heat-press, use 320-330 degrees for 10-12 seconds, then turn garment over and press from the back-side for 15-20 seconds more. If using a hand iron, use setting between Wool and Cotton, no steam. Use same dwell times. You're done!
1-5 business days
Buyers are responsible for any customs and import taxes that may apply. I'm not responsible for delays due to customs.
Request a cancellation within: 3 hours of purchase
But please contact me if you have any problems with your order.
They are sent first class with a stamp on a plain white or manilla envelope. There is no tracking information on these unless you upgrade to Priority Mail.
On the patches, if you look in the item description, the sizes of the individual patch is listed.
Dec 29, 2019
Dec 1, 2019
Amazing patches!!!!!
Jul 20, 2018
looks great! arrived quickly, looks just like expected
Apr 24, 2018


text:
"We had Magnation installed 2 weeks ago. At first, the results were very subtle. This is because the new filtered water is being mixed with unfiltered water in a hot water heater. As days progressed, the results were dramatic. Today, gone are water spots on dishes, red/iron rings in toilets, dry hair and dry skin. We are so pleased with just these positive results that if that's all it does...we are elated! However, I believe these amazing results are just the beginning. Future economic benefits to come.. less soap/longer appliance life/beautiful gardens/plants and chemical-free water softening without the hassle. Absolute professional sales rep/professional installation (human actually answers phone!). Look at price as an investment. The long term benefits are huge and are the measure of money well spent."
~ Corinne Kliegl, Cave Creek, Arizona


text: Be your own best friend! How can you be a friend to someone else if you can't be a friend or be honest with yourself? Even if you can't be honest with anyone else be honest with yourself. Learn how to be alone and not be lonely! It may sound odd to some people but you can be alone and not be lonely. The same way you can be in a room full of people and feel alone. Learn how to enjoy being by yourself, love your own company. If you like YOU others will too!


text:
Functions on the Inspection Application:
While the primary function of the Inspection app is to conduct inspections, you can also access owner, property, tenant and creditor information. The app performs in much the same way Palace does.
You have an owner list, which in turn shows you the properties that you manage for each owner (as well as providing contact details), the property list which displays the owner and tenant in that property, and the tenant list. You can click on any of the lists to get started.
If you want to conduct a property inspection, you need to start by touching the property button. The Inspections button is only used to view, upload or delete finished or partially finished inspections.
Owner List You can use your finger to scroll up and down the owner list. When you touch an owner name, the details on the right-hand side of the screen change to display the details of that owner. You can also use the search function at the top of the list to search for particular owners. If you touch the email address, then a menu appears which asks if you want to send an email to the owner. If you are running this on the iPhone, and you touch a phone number, then you have the option to call or send a text message as well. If you touch one of the properties that you manage for the owner, then you are taken to the property list.
NOTE: That text messages and emails done on the iPhone do NOT get saved back in Palace.
Property List The property list behaves in the same way that the owner and tenant lists do. The main difference being that the details area of the screen are different. In this example, we can see who the owner of this property is, but there is no tenant which would otherwise appear below the owner name. From this screen you can either commence the inspection of the property, configure the inspection, do a video inspections, see the disbursement level and create a works order.
- If you touch the property address next to the image of the map, then a menu appears with the options to view a map of where the property is, or to get directions.
- If you touch the View Map option, then you are able to get back to the property by clicking the word Back.
- If you touch the Get Directions option, then the mobile device will open the Google Maps program. Because this is a separate app, you cannot click the Back button. Instead you will need to double-click the iPad or iPhone button (there is only 1 button), which will allow you to go back to the Palace App.
New Inspection: This will bring up the old inspection ready for you to override New Empty Inspection: This will bring you up a completely empty inspection, it will delete any old information. It will warn you so make sure this is really what you want to do.
Configure Inspection: When you enter in a new property, you should always configure your template to match this property. See more information on this below New Video Inspection: Click on this to do a video inspection - More instructions below Disbursements: This will let you know if the owner has a limit on the amount of money you can spend without letting him know, this feeds from the Property edit screen in Palace. New Works Order: You can create a works order for this property and it will be printed or emailed in Palace.
Tenant List The tenant list shows basic information relating to each tenant in your portfolio. Specifically you can see the rent rate, rental period, the start date and paid-to date of each tenancy. This information updates the next time you export from Palace and sync again.
Creditor List The last available list on the app is unrelated to the owners, properties or tenants. It is the creditors (or tradespeople) available to you. The information is provided to help you get the contact details of tradespeople for required maintenance.


text:
Ron Browz releases a visual for "Bye," his ode to hitting it and quitting it. On the track Ron also raps (if you want to call it that) about ghostwriting for other artists. I wonder who this man is getting checks from?
Ron Browz – Bye (Official Music Video)
Ron Browz – El Chapo (Remix) (Feat. 2 Milly, Dave East, N.O.R.E., Smoke DZA & Cory Gunz)
Ron Browz connects with several New York artists on the official remix of "El Chapo".
Ron Browz – She Don't Like Me (Feat. Remy Ma) (Official Music Video)
Ether Boy Ron Browz returns with the visual for "She Don't Like Me" with a guest appearance from Remy Ma. Directed by Last American…
Ron Browz – She Ain't Nothin' To F Wit (Feat. Raekwon)
Ron Browz teams up with Raekwon for the official remix of his "She Ain't Nothin' To F Wit" record inspired by Wu-Tang.
Ron Browz – Butter (Official Music Video)
Ron Browz releases the official music video for his "Butter" joint.
Ron Browz – Handle It (Feat. Tony Yayo)
Ron Browz drops off a new freebie "Handle It" featuring Tony Yayo. His She Got It project is coming soon.
LL Cool J – I'm Nice (Feat. Raekwon, Murda Mook & Ron Browz)
Legendary emcee LL Cool J collaborates with Raekwon, Murda Mook, and Ron Browz on "I'm Nice," a new song from his upcoming G.O.A.T. 2…
Shawty Lo – Hundredz (Feat. Ron Browz & Waka Flocka)
Shawty Lo connect with Ron Browz and Waka Flocka for "Hundredz" in support of his King Of Bankhead project dropping on July 4th.
Ron Browz – Harlem Brooklyn Finest (Feat. Papoose)
Ron Browz and Papoose link up on a new record titled "Harlem Brooklyn Finest," which will appear on the upcoming mixtape The Christening 2,…
Rising New York artist Sean Scott drops off a new single titled "Skyline." The track is produced by Ron Browz and will live on…
Ron Browz – Real Ni**a (Feat. N.O.R.E.)
Ron Browz and N.O.R.E. link up for another new collaboration titled "Real Ni**a". Check out their previous track together "Rollin" here.
Ron Browz – Rollin (Feat. N.O.R.E.)
Ron Browz enlists the services of N.O.R.E. for his newest single "Rollin". Download: Ron Browz – Rollin (Feat. N.O.R.E.)
I'm definitely not posting this video because I like the song…
Ron Browz – Don't Cross Me (Feat. Tony Yayo & Karty)
At first glance you may think this track may fall by the recycling bin, but surprisingly this is a dope track. Enjoy. Source: Thisis50
Ron Browz – On My New Sh*t (Feat. Busta Rhymes & Reek Da Villain)
I regret to say we have some new Ron Browz, the other verses from Reek and Busta are dope but isn't auto-tune yesterday? Source:…
Nope, this isn't a joke. You though the "Tupac Back" dead artist remakes were done right? They aren't. Here's the latest from Ron Browz…
Ron Browz – Party Till The Morning (Feat. Lloyd Banks)
New music from The Ether Boy and Lloyd Banks. Same basic format Ron Browz goes with every time. This time it features a Banks…
The Latest
Future "Perkies" (Produced by Metro Boomin)
Debonair Brown "Embrace It" (Official Music Video)
A Boogie Wit da Hoodie "Reply" (Feat. Lil Uzi Vert)
Future "Last Name" (Feat. Lil Durk)
Lil Peep "Everybody's Everything" (Album Stream)
Tory Lanez "Chixtape 5" (Album Stream)
Kanye West "Jesus Is King" (Album Stream)
Kirill & Jaco "Hublot" (Official Music Video)
Lil X "New Kid on the Block" (Album Stream)


text:
Donation of necessary equipments for Halawalkelle Primary School Meegahathenna
Wes/Mathu/ Halawalkelle Primary School situated at Meegahathenna (Mathugama Zone) presently studying a 52 Students under the minimum requirements with staff of 08 Teachers. Most of the parents of the students are uneducated and working as labourers of the near by Tea estates and also high percentage of the students are facing for the numerous illness due to malnutrition.
Principal of the School Mr. Chaminda Aluthge made a request Arunalu Group to provide few essentials required for the students. (Requested letter attached herewith).
Please contact for further details and contributions:
Mr. Jayanath – 0714848090


text:
Written while watching the rain fall.
I am back with another makeup Monday to sooth you Monday blues away. Grab a drink, get cozy, and let's get started!
I was at Ulta on Saturday, of course, and Urban Decay was there doing makeup as sort of a promotional thing. They had all of the UD cosmetics right in front of the store, and I was sucked in! I have wanted to try this Weightless Complete Coverage Concealer for awhile since I have heard so many good things about it, so picked it up in the color fair neutral. I think might be a little too light for me but don't you worry, ill make it work. Yours for $28.
I heard about this product from YoutTubers's ReadySetGlamour's April favorites video. It is a 360° Eye Perfecting Primer (couldn't find it on Ulta's website) that is supposed to give you the appearance of not having under eye lines. She speaks very highly of this product, and when I was at Ulta, I happened to see it and figured I would give it a try. I wore it last night under my foundation and concealer, and I can't say I noticed a difference but hopefully, I will the next few times I wear it. This eye gel is $26 which I think is stupid expensive for .18 oz.
I am sure everyone has heard about Make Up For Ever Step 1 Skin Equalizer Mattifying Primer, but I just bought it, so I am going to talk about it. I decided to order this primer on Sephora.com because I was feeling like my regular Beneulfit POREfessional's primer wasn't keeping me matte enough with the warmer weather. I wore the Makeup Forever Primer to work on Friday, and I didn't notice a huge difference but hopefully, with continued use I will. At Sephora for $37.
Thanks for reading and I'll see you soon! Still looking for a Mother's Day gift? Click here.


text:
The University of Brighton end of year show
Location: Hastings Pier
Open to the public: Tuesday 5th – Sunday 10th June
Saturday 9th free space – A day food, celebration, school & community events
Free entry
The University of Brighton's School of Architecture and Design is delighted to announce that its annual graduate show will take place on Hastings Pier.
Hastings Pier recently awarded the RIBA's Stirling prize, hosts a wide range of activities. This Year's student show will coincide with a monthly food market, outdoor performances of A Midsummer Night's Dream and the regions annual 1066 cycle festival. Saturday will include talks by designers and architects, including the Pier's architect.
Full details on the show can be found here.


text:
Securing Compensation For Tractor Trailer Injuries
If you have driven on the major South Carolina roadways including I-77, I-26, and I-20, you know first hand that 18 wheelers and logging trucks can be dangerous.
The trucking industry is indispensable, transporting goods that we as South Carolinians use on a day to day basis. Our reliance creates a huge responsibility for truck drivers who spend countless hours delivering us the services we need. When a tractor trailer or logging truck gets into the wrong hands, the consequences can be deadly.
Tractor trailer accidents occur for a number of reasons including:
- driver fatigue and exhaustion,
- overloaded or oversized trucks,
- speeding, reckless or aggressive driving, and
- lack of training
According to the Federal Motor Carrier Safety Administration (FMCSA), the two most common driver related factors which result in an accident are failure to keep in the proper lane and driving too fast. Given the amount of force resulting from the impact of a tractor trailer accident can result in permanent disability or even death.
Common tractor trailer injuries include:
- disfigurement,
- head, neck and spinal trauma, and
- a claim for wrongful death.
If you or a loved one has been injured or even killed as a result of tractor trailer accident, you may be entitled to compensation for your injuries including lost wages, current and future medical bills, funeral expenses, pain and suffering, and depending upon the facts of your case, punitive damages to punish the at fault driver for his actions.
The South Carolina tractor trailer wreck attorneys at the Strom Law Firm, L.L.C. have the resources and experience you need to thoroughly investigate your case and secure the compensation you deserve. Contact the Strom Law Firm, L.L.C. today at 803.252.4800 for a free no-cost consultation to discuss the facts of your case.


text:
No single individual in human history ever planned out a road map, or assembled a recipe of ideal ingredients for building a holistic civilization — just as no one has ever planned to write the book, poem, or musical composition that will later become a classic.
At any given time in history there is only one civilization going on; one civilization, spearheaded by ideals, fuelled by advances in many endeavors of human life, and led by individuals. Some become famous; most do not.
The ideals of civilization include respecting the freedoms and human rights of the individual; encouraging and rewarding innovations and creativity; and living by the light of reason, rationality, scientific awareness, equity, and justice.
When the recognized leaders of a civilization stop living by the ideals which singled them out for leadership in the first place, those leaders die. Yet civilization will always find new leaders to carry on. They may be unknown, living far away, part of a different ethnic community, or even adherents of a different religious faith. But they will nevertheless emerge as leaders.
Muslim civilization took over from other ancient civilizations when their leaders abandoned, or forgot how to live by, their founding ideals. Similarly, when the leaders and citizens of Muslim civilization stopped living authentically in Islam, this civilization found new leaders, often in the West.
Today, we are living in a Western-led civilization; thus, if Muslims aspire to lead, then they must learn and understand the state of the art that drives such a civilization — that is, both its strengths and weaknesses. They must offer a viable example, an alternative way, showing how living in Islam can enhance today's civilization. But they must also earn that leadership; in so doing, the whole world will naturally turn to them to lead.
We hear people saying that Muslims need only wait for the current Western-dominated world to collapse under the weight of its own weakness. But such an approach is impractical, unhealthy, and above all, wrong. Whether they acknowledge it or not, Muslims are contributing to today's civilization; they have responsibilities to it and can only contribute to its decay by choosing to stand by and do little, or nothing. Worse still, they can exert a negative impact on it through (for example) promoting policies of extremism, fanaticism, or tribalism.
Alternatively, if Muslims truly and consciously choose to live wholly in the ideals of Islam, they could gain the collective moral power to save today's civilization — our civilization — as well. This is not about the old, but persistent "clash of civilizations" theory; quite the opposite.
The "clash of civilizations" idea is a trap, plain and simple, because it tries to explain political conflicts based purely on the confrontation between competing values and cultures, between arbitrarily defined "right" and "wrong." Even more sinister is the fact that this destructive theory has been dished out far and wide to account for the roots of any political strife between today's rich and powerful Western bloc, and the so-called "third," or "developing" world.
According to this premise, there is no need to study the roots of any conflict in depth, or to try and solve it along culturally informed lines, because purveyors of the "clash of civilizations" view see only a black and white scenario; two competing world views, two competing non-negotiable value systems. The West is seen as being good, right, and culturally advanced. Everyone who differs with it, militarily or politically, is seen as evil, wrong, and less-evolved.
Clearly, the "clash of civilizations" is a racist theory and Muslims should categorically reject it. Muslims also should not buy into the parallel theory that more than one civilization can be happening on earth at any given time; the idea of coexisting civilizations is purely in the realm of science-fiction, an obvious trap for anyone who fails to think deeply about who we all are as human beings.
While our own ancestors in Qurtuba, Baghdad, Cairo and Damascus made enduring and substantial contributions to today's modern civilization, remember that the ancient societies of Egypt, Greece, India, and China also did so.
We Muslims are shareholders in today's civilization. Too many of us may be passive shareholders, but we are nevertheless part of the big picture. The problem is that we are not developing our cultural investment in the world. Too few Muslims are leading today's civilization. We desperately need more and better leadership, leadership born of a renewed global Muslim Ummah that truly lives Islam. And it is not an optional choice. Living Islam is who and what we are. Without it, one may be breathing and biologically alive, yet spiritually dead.
How can we demonstrate that living Islam is both good for us and others? The key is to live by example, showing the world that when Muslims truly live Islam, it benefits everyone. Fortunately, Muslims have been blessed with excellent tools to help and guide the individual to live Islam fully. We have the science and discipline of Sufism, for example.
We have the three levels of living Islam; to know, to love, and to serve. The first step is about coming to know God — through divine creations, one's own being, the purpose of our life on earth, our life after physical death, and our final destination in oneness with God. The second step is coming to love God — again through the wonder of divine creations, one's own being, in the sacred gift of life, and in meeting God through our daily activities and awareness. Finally, the third step is to learn to serve God — in preserving and respecting all of creation, in caring for others and oneself, in giving God our daily praise and prayer.
The order in which we learn these steps is very important, for one cannot love someone who is unknown, nor can anyone genuinely serve someone they do not love. Ideally, however, the steps of knowing, loving and serving should be pursued in parallel, so that even as imperfect human beings, we can always be in the blessed state of knowing a little, loving a little, and serving a little.
This is the way we Muslims can actively be part of today's civilization, our civilization.
Mohamed Elmasry is a professor of electrical and computer engineering at the University of Waterloo and national president of the Canadian Islamic Congress.


text:
Ever fantasize about that perfect island getaway? Not all airways allow preassigned seats. Join the hundreds of thousands of consumers which have used to find low cost aircraft tickets. Business and First Class airfares are additionally available for buy. Previous to turning into a journalist and client advocate, he worked in airline flight operations administration for seven years.
Cebu Pacific & AirAsia Zest regularly provide the perfect offers to Philippines flights, or select your preferred provider under to see the most affordable days to fly. Transatlantic airfares are going up. We all want the cheapest flights potential! As a substitute, take a look at Wotif's value-friendly airfares on flights to Melbourne and book one now so you possibly can go shopping at Queen Victoria Market, the biggest open-air market within the Southern Hemisphere.
Select from Qantas, Virgin Australia, Emirates, Singapore Airways, Air New Zealand, Cathay Pacific, Thai Airways, Etihad, Malaysia Airways and extra. You may receive early notifications for airfare gross sales and different great promotions – and gain the flexibility to gather and redeem WestJet dollars, which could be spent anytime, with out blackouts.
With options like Prompt Discounts, Fare Calendar, MyRewards Program, MyWallet and plenty of extra, the …


text:
Submit a request
Sign in
Alabama Department of Revenue Help Center
Frequently Asked Questions: Dealer License
New articles
New articles and comments
What are the requirement for an off-site license?
Is there a fee for making a change to my regulatory license?
Is there a charge for each location?
What do I need to do if I move from my licensed location?
How do I reprint my license?
When will my license be mailed?


text:
We supply carpet for events, exhibitions and events. Whenever your company is present at an industry event, congress or exhibition, you'll want to make sure you impress your visitors. The right look and feel is important, so you should use your furniture and stand design to represent your company. Floor coverings are an essential part of your presentation; use of high-quality carpet emphasises the character of your stand. JMT helps you create the look and feel you desire. With high-quality carpets, for any budget, and reliable service and supply, JMT is the partner for you!
Our polyamide ranges of carpets are available in various colours, widths and types, which can be used for many occasions.
Carpet for any occasion
The different types we provide are:
- Las Vegas/Miami
- New Mambo
- Charmant/Castello
- Metro/Traffic
- Sparkling/Aruba
- Sisal
- Vinyl
- Artificial Grass
- Laminate
- Needle Felt Carpet
- Rubber
- Printed Carpet
- Carpet tiles
About JMT's conference and office furniture
JMT is one of the largest suppliers of event furniture and floor coverings for the exhibition market across Europe. We have a wide product range of top quality event furniture and floor coverings. In order to provide the best service possible, we attend many exhibitions throughout the UK and Europe giving us a detailed understanding of most venues and ensuring that we provide an efficient and high-quality service.
Also have a look at our event furniture for events and exhibitions. Do you have questions, special requirements or suggestions? Then please contact us. We're always looking for feedback and suggestions to improve and innovate our products and services.


text:
Do you do things like this? Go to Goodwill, wander over to the shambles that is the Home department, idly finger some atrocious plastic placemats and think, "These are so Christopher Kane Spring 2011."
Regardless, you will like these neon lace clutches you can make from placemats, some vinyl and a zipper for an easy spring or summer accessory.
These cost me a dollar a piece to make (compared to $530 for the real ones from Christopher Kane.) Plus, you can drop these in the pool with no lasting harm.
My tutorial is featured over at examiner.com and includes a step-by-step slideshow.


text:
If a student wishes to change their major, they must contact the Admissions Office and complete the change of major form. If the change of major form is submitted within the first five (5) days of the term, the change occurs at that point. If the form is submitted after the fifth (5th) day of the term, the change will become effective at the start of the next term.
During a student's first term of enrollment, they may have only one declared major. Beginning with the second term of enrollment, a student may request to have a second major added to their record. A student may not have more than two active majors at any given time.
Approved by: Leadership Council
Effective Date: 03/23/15
Last Date Revised: 12/05/14


text:
As you can imagine, reduce the list to only 10 is very difficult and we had to exclude several, one of which was longly debated, therefore presented as a special guest here:
Monica Vitti
Monica Vitti, born Maria Luisa Ceciarelli, born November 3, 1931, in Rome, is a particularly famous Italian actress mainly linked to the cinema of the past.
For almost forty years Monica Vitti has been one of the most promising Italian movie stars, accompanied by her unmistakable raucous voice and her blonde hair.
At the base of his professional training is the diploma obtained at the Silvio D'amico Academy of Dramatic Arts, following which he began his participation on the stage. Monica Vitti's childhood saw her spend eight years in the city of Messina before deciding to return to the capital with her family. Her talents as an actress emerged during the war, in which she often found herself using puppets as toys.
Thanks to the director Mario Monicelli Monica Vitti gets the lead role in the film La ragazza con la pistola (1968), later participating in the film Drama of Jealousy – All the details in chronicle (1970) by Ettore Scola, La Tosca (1973 ) by Luigi Magni, joining Alberto Sordi, Miklós Jancsó, Luis Buñuel in The Phantom of Freedom (Le fantôme de la liberté) (1974) and André Cayatte in State Reason (La raison d'état) (1978).
have a look at
TOP 10 of the most iconic Italian cars of all time
10 cars representing the most iconic style and touch of Italian car manufacturers
TOP 10 of the most iconic Italian foods of all time
10 foods representing the culture, the history, and obviously the great taste that Italy can offer to the world. As no one else.
TOP 10 of the most iconic Italian actresses of all time
10 actresses that with their talent, beauty and charm have represented the Italian culture at its best in the seventh art. Cinema.


text:
Months ago, I stumbled across Konkuri thanks to the Download Squad. It lets you organize tournaments painlessly with a good range of customization such as round robin or bracket tournaments, the number of rounds per set, and randomly generating matches.
The real beauty of Konkuri is that when you register for a free account, all your tournaments are permanently saved to the database to view for posterity. For example, this past afternoon, I held an amateur tournament for the CSULB Gaming Club. Here are the results to the past games.
Tekken 6 singles, round robin
Brawl 2v2 teams, round robin
Brawl 2v2 ver.2, single elimination
The only feature missing that I wish it had was double elimination. Fortunately, I got a hold of another tournament organizing software, tio. Double elimination is a much more speedy way to get through the matches while still giving everything ample chances to win. Of course, since its software, it's not available for public viewing, but you can save files for easy viewing later. Here's a screencap of the Blazblue singles tournament with double elimination.


text:
With the sun shining brightly in the sky, it was time Michael and Megan to commit their lives to one another in the bond of marriage at the always stunning Broyle Place near Ringmer. The whole day was a very relaxed and fun filled with lots of laughter and tears. The dress was a beautiful flowing number from the Fross Wedding Collections in Uckfield topped off with a stunning veil which helped to make Megan such a stunning bride, while the guys sweated it out in their tweed suits which Michael chose personally, probably not the best choice on a hot summers day.
The surprise of the day came later, when the Tailored Tenors disguised as waiter arrive to entertain all the guests during the reception.
Ceremony & Reception: Broyle Place, Ringmer
Dress: Fross Wedding Collections
Singers: Tailored Tenors
Second Shooter: Chris Aldous Photography


text:
Creating a cohesive Instagram feed is an extremely daunting task. There is the colour scheme, making sure it all flows, editing of the images and not to mention the planning! The Instagram makeover package is here to assist you in obtaining your dream Instagram feed, that perfectly reflects your brand and showcases your product or services in the best way possible. After you fill out the Instagram Makeover form, to give me an idea of the style you are wanting to achieve and your struggles and I will then come up with a plan. A mood board will be created to reflect the colour scheme and types of photos you will be posting. During this time it is an ideal time to find photos of your products and send them to me. Don't worry, if you do not have photos of your products or you are a service based business I can source photos or stock images can be purchased. I will create a custom filter, reflecting the look and style you are wanting achieved. I then edit the photos and plan your new Instagram feed.
You will receive a guide that helps you with implementing your new theme. It includes your mood board, filter and planned feed. As well as information on the importance of colour scheme, editing, planning and must have apps!
Price: $150


text:
International Double Master in Biomedical Sciences (IMBS)
The double Master Program in Biomedical Sciences (IMBS) is offered by the Institute of Molecular Medicine and Cell Research at the Medical Faculty of the Albert-Ludwigs-University of Freiburg (ALU), one of Europe's oldest and highly respected universities in cooperation with the University of Buenos Aires (UBA), Argentina, which has a leading role in Latin America.
This international Master Program offers a double Master degree from both universities. The program is tailored to the interests of international graduate students in life and natural sciences and medicine with professional experience. It is designed as a two years full-time study and research program with specific and practical training that qualifies for success in academia or the private sector.
City of Buenos Aires
Buenos Aires is the largest city in Argentina, located on the shores of the Río de La Plata and home to about 300,000 students. It is a modern, dynamic and radiant city with an intense cultural life where tango long coffee klatches and football (soccer) are essential elements in its people's daily lives.
City of Freiburg
Freiburg is home to many students turning it into a prominent and ever-growing academic hub in one of Germany's vibrant and multicultural cities. Located in Baden-Württemberg near the French and Swiss border, surrounded by the black forest, it's well-known for its variety of recreational and cultural activities.
Biomedical sciences combine knowledge and questions of experimental medicine with methods of molecular biology and cell biology.
The IMBS curriculum is designed to promote not only the technical skills required for success in research, but also impart skills that are indispensable for a successful and responsible scientist.
The program starts at UBA in Buenos Aires for 8 months with a basic unit conveying general knowledge including some practice in molecular medicine and biochemistry. The next 8 months take place at ALU in Freiburg including 5 modules of laboratory research (and 5 months) to deepen theoretical knowledge, to enable the judgement of scientific papers with a bioethical basis, to obtain competences in lab research methods including individual supervision and to learn own scientific strength and focus.
In addition, the students take part in intensive Spanish and German language courses, in scientific and intercultural communication training and in a special designed lab training.
The last 8 months are dedicated to the master thesis project which can be done at either institution.
To date, 98% of the international IMBS graduates have successfully completed the master program. IMBS students are from all continents and long-lasting friendships have been developed.
The students will be supported by the IMBS coordinators at both universities, by former students (alumni) and by mentors of the program.
Successful students of the IMBS program will be awarded a double degree, a Magister in Biomedical Sciences by UBA and a Master of Science (MSc.) in Biomedical Sciences by ALU, accumulating 120 ECTS points, recognized worldwide.
How do I apply?
Applications are accepted until 31st July for the next year's program.
For more information see our application website.