Situated in the heart of the Dandenong Ranges within tranquil treetops location, this luxurious, comfortable and spacious home will capture your senses and appeal to anyone desiring a hills retreat with simply nothing to do but move in, relax and enjoy.
Set over two levels and elevated inviting an abundance of sunlight, this extensive residence oozes opulence from the moment you walk into the commanding entrance to a modern, functional floor plan completed with quality fixtures and fittings. The windows frame the views at every corner in the lounge with seating nooks creating perfect places to relax and a wood fire adding to the ambience.
A superb kitchen with granite benchtops and quality S/S appliances adorn the wall to wall cabinetry and overlook the spacious meals and outdoor entertainment patio. A home office adjacent to the foyer creates an ideal work from home space with ample storage and powder room while internal access from the double remote garage is well designed.
The upper level reveals a spacious master suite off the landing and a stylish walk through robe with floor to ceiling fit out leading to the resort style bathroom will simply take your breath away. Luxurious appointments include double shower, twin vanity and deep soaker bath with mezzanine sitting area connecting two further bedrooms, one ensuited, while the options are endless as this fabulous home offers so much more.
Mountain Element B n B is a place of peace, relaxation and balance, enjoyed by many guests and in a class of its own. A separate entrance to the retreat leads to a living room with a gas log fire and opening to a private balcony to take in the treetop views. The king-size bedroom and ensuite complete this immaculately maintained home.
Mountain Element is a place that demands inspection to be truly appreciated.


1.1 The Importance of Communication In a survey conducted by the Katz Business School at the University of Pittsburgh, organizations rated communication skills as the most important factor used in selecting their management staff. The study found that oral and written communication skills were important in predicting job success, as was the ability to communicate well with others in the... Download Presentation Technical Communication Skills An Image/Link below is provided (as is) to download presentation. Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.
Adopting a direct, functional, and practical approach, the book presents an exhaustive treatment of the basics of technical communication, both oral and written.
Importance of Technical Communication • Communication serves as an instrument to measure the success or growth of an organization • Technical communication in an organization can be divided into two parts: – Oral and – Written. .
Strategies for Technical Communication in the Workplace incorporates relevant technology coverage and stresses the importance of thinking about global audiences wherever relevant. INSTRUCTOR SUPPORT Instructor's Manual, by Lee Scholder, J.D., University of Minnesota and Daun Daemon, North Carolina State University.


text:
[Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01 02 draft-ietf-ace-key-groupcomm
ACE Working Group                                           F. Palombini
Internet-Draft                                               Ericsson AB
Intended status: Standards Track                               M. Tiloca
Expires: April 25, 2019                                          RISE AB
Key Provisioning for Group Communication using ACE
draft-palombini-ace-key-groupcomm-02
This document defines message formats and procedures for requesting
and distributing group keying material using the ACE framework, to
protect communications between group members.
Drafts is at https://datatracker.ietf.org/drafts/current/.
Palombini & Tiloca       Expires April 25, 2019                 [Page 1]
Internet-Draft  Key Provisioning for Group Communication    October 2018
3.  Authorization to Join a Group . . . . . . . . . . . . . . . .   5
3.1.  Authorization Request . . . . . . . . . . . . . . . . . .   6
3.2.  Authorization Response  . . . . . . . . . . . . . . . . .   7
3.3.  Token Post  . . . . . . . . . . . . . . . . . . . . . . .   8
4.  Key Distribution  . . . . . . . . . . . . . . . . . . . . . .   8
4.1.  Key Distribution Request  . . . . . . . . . . . . . . . .   9
4.2.  Key Distribution Response . . . . . . . . . . . . . . . .  10
5.  Removal of a Node from the Group  . . . . . . . . . . . . . .  12
5.1.  Expired Authorization . . . . . . . . . . . . . . . . . .  12
5.2.  Request to Leave the Group  . . . . . . . . . . . . . . .  12
6.  Retrieval of Updated Keying Material  . . . . . . . . . . . .  13
6.1.  Key Re-Distribution Request . . . . . . . . . . . . . . .  13
6.2.  Key Re-Distribution Response  . . . . . . . . . . . . . .  13
7.  Retrieval of Public Keys for Group Members  . . . . . . . . .  13
7.1.  Public Key Request  . . . . . . . . . . . . . . . . . . .  14
7.2.  Public Key Response . . . . . . . . . . . . . . . . . . .  14
8.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
10.2.  Informative References . . . . . . . . . . . . . . . . .  16
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  17
This document expands the ACE framework [I-D.ietf-ace-oauth-authz] to
define the format of messages used to request, distribute and renew
the keying material in a group communication scenario, e.g. based on
multicast [RFC7390] or on publishing-subscribing
[I-D.ietf-core-coap-pubsub].
Profiles that use group communication can build on this document to
specify the selection of the message parameters defined in this
document to use and their values.  Known applications that can
benefit from this document would be, for example, profiles addressing
group communication based on multicast [RFC7390] or publishing/
subscribing [I-D.ietf-core-coap-pubsub] in ACE.
If the application requires backward and forward security, updated
keying material is generated and distributed to the group members
(rekeying), when membership changes.  A key management scheme
performs the actual distribution of the updated keying material to
the group.  In particular, the key management scheme rekeys the
current group members when a new node joins the group, and the
remaining group members when a node leaves the group.  This document
provides a message format for group rekeying that allows to fulfill
these requirements.  Rekeying mechanisms can be based on [RFC2093],
[RFC2094] and [RFC2627].
document are to be interpreted as described in [RFC2119].  These
words may also appear in this document in lowercase, absent their
normative meanings.
Readers are expected to be familiar with the terms and concepts
described in [I-D.ietf-ace-oauth-authz] and [RFC8152], such as
Authorization Server (AS) and Resource Server (RS).
+------------+                  +-----------+
|     AS     |                  |    KDC    |
|            |        .-------->|           |
+------------+       /          +-----------+
^             /
|            /
v           /                           +-----------+
+------------+   /      +------------+        |+-----------+
|   Client   |<-'       | Dispatcher |        ||+-----------+
|            |<-------->|    (RS)    |<------->||   Group   |
+------------+          +------------+         +|  members  |
+-----------+
Figure 1: Key Distribution Participants
The following participants (see Figure 1) take part in the
authorization and key distribution.
o  Client (C): node that wants to join the group communication.  It
can request write and/or read rights.
o  Authorization Server (AS): same as AS in the ACE Framework; it
enforces access policies, and knows if a node is allowed to join
the group with write and/or read rights.
o  Key Distribution Center (KDC): maintains the keying material to
protect group communications, and provides it to Clients
authorized to join the group.  During the first part of the
exchange (Section 3), it takes the role of the RS in the ACE
Framework.  During the second part (Section 4), which is not based
on the ACE Framework, it distributes the keying material.  In
addition, it provides the latest keying material to group members
when requested.  If required by the application, the KDC renews
and re-distributes the keying material in the group when
membership changes.
o  Dispatcher: entity through which the Clients communicate with the
group and which distributes messages to the group members.
Examples of dispatchers are: the Broker node in a pub-sub setting;
a relayer node for group communication that delivers group
messages as multiple unicast messages to all group members; an
implicit entity as in a multicast communication setting, where
messages are transmitted to a multicast IP address and delivered
on the transport channel.
This document specifies the message flows and formats for:
o  Authorizing a new node to join the group (Section 3), and
providing it with the group keying material to communicate with
the other group members (Section 4).
o  Removing of a current member from the group (Section 5).
o  Retrieving keying material as a current group member (Section 6
and Section 7).
o  Renewing and re-distributing the group keying material (rekeying)
upon a membership change in the group (Section 4.2 and Section 5).
Figure 2 provides a high level overview of the message flow for a
node joining a group communication setting.
C                              AS     KDC   Dispatcher          Group
|                              |       |        |               Member
|                              |       |        | \               |
|     Authorization Request    |       |        | | Defined       |
|----------------------------->|       |        | | in the ACE    |
|                              |       |        | | framework     |
|     Authorization Response   |       |        | |               |
|<-----------------------------|       |        | |               |
|                              |       |        | |               |
|--------- Token Post ---------------->|        | /               |
|                                      |        |                 |
|---- Key Distribution Request ------->|        |                 |
|<--- Key Distribution Response ------ | --- Group Rekeying ----->|
|                                               |                 |
|<================== Protected communication ===|================>|
Figure 2: Message Flow Upon New Node's Joining
The exchange of Authorization Request and Authorization Response
between Client and AS MUST be secured, as specified by the ACE
profile used between Client and KDC.
The exchange of Key Distribution Request and Key Distribution
Response between Client and KDC MUST be secured, as a result of the
ACE profile used between Client and KDC.
All further communications between the Client and the KDC MUST be
secured, for instance with the same security mechanism used for the
Key Distribution exchange.
All further communications between a Client and the other group
members MUST be secured using the keying material provided in
3.  Authorization to Join a Group
This section describes in detail the format of messages exchanged by
the participants when a node requests access to a group.  The first
part of the exchange is based on ACE [I-D.ietf-ace-oauth-authz].
As defined in [I-D.ietf-ace-oauth-authz], the Client requests from
the AS an authorization to join the group through the KDC (see
Section 3.1).  If the request is approved and authorization is
granted, the AS provides the Client with a proof-of-possession access
token and parameters to securely communicate with the KDC (see
Section 3.2).  Communications between the Client and the AS MUST be
secured, and depends on the profile of ACE used.
Figure 3 gives an overview of the exchange described above.
Client                                            AS  KDC
|                                               |   |
|---- Authorization Request: POST /token ------>|   |
|<--- Authorization Response: 2.01 (Created) ---|   |
|----- POST Token: POST /authz-info --------------->|
|                                                   |
Figure 3: Message Flow of Join Authorization
3.1.  Authorization Request
The Authorization Request sent from the Client to the AS is as
defined in Section 5.6.1 of [I-D.ietf-ace-oauth-authz] and MUST
contain the following parameters:
o  'grant_type', with value "client_credentials".
Additionally, the Authorization Request MAY contain the following
parameters, which, if included, MUST have the corresponding values:
o  'scope', with value the identifier of the specific group or topic
the Client wishes to access, and optionally the role(s) the Client
wishes to take.  This value is a CBOR array encoded as a byte
string, which contains:
*  As first element, the identifier of the specific group or
topic.
*  Optionally, as second element, the role (or CBOR array of
roles) the Client wishes to take in the group.
The encoding of the group or topic identifier and of the role
identifiers is application specific.
o  'req_aud', as defined in Section 3.1 of
[I-D.ietf-ace-oauth-params], with value an identifier of the KDC.
o  'req_cnf', as defined in Section 3.1 of
[I-D.ietf-ace-oauth-params], optionally containing the public key
or the certificate of the Client, if it wishes to communicate that
to the AS.
o  Other additional parameters as defined in
[I-D.ietf-ace-oauth-authz], if necessary.
3.2.  Authorization Response
The Authorization Response sent from the AS to the Client is as
o  'access_token', containing the proof-of-possession access token.
o  'cnf' if symmetric keys are used, not present if asymmetric keys
are used.  This parameter is defined in Section 3.2 of
[I-D.ietf-ace-oauth-params] and contains the symmetric proof-of-
possession key that the Client is supposed to use with the KDC.
o  'rs_cnf' if asymmetric keys are used, not present if symmetric
keys are used.  This parameter is as defined in Section 3.2 of
[I-D.ietf-ace-oauth-params] and contains information about the
public key of the KDC.
o  'exp', contains the lifetime in seconds of the access token.  This
parameter MAY be omitted if the application defines how the
expiration time is communicated to the Client via other means, or
if it establishes a default value.
Additionally, the Authorization Response MAY contain the following
o  'scope', which mirrors the 'scope' parameter in the Authorization
Request (see Section 3.1).  Its value is a CBOR array encoded as a
byte string, containing:
*  As first element, the identifier of the specific group or topic
the Client is authorized to access.
roles) the Client is authorized to take in the group.
The access token MUST contain all the parameters defined above
(including the same 'scope' as in this message, if present, or the
'scope' of the Authorization Request otherwise), and additionally
other optional parameters the profile requires.
When receiving an Authorization Request from a Client that was
previously authorized, and which still owns a valid non expired
access token, the AS can simply reply with an Authorization Response
including a new access token.
3.3.  Token Post
The Client sends a CoAP POST request including the access token to
the KDC, as specified in section 5.8.1 of [I-D.ietf-ace-oauth-authz].
If the specific ACE profile defines it, the Client MAY use a
different endpoint than /authz-info at the KDC to post the access
token to.  After successful verification, the Client is authorized to
receive the group keying material from the KDC and join the group.
Note that this step could be merged with the following message from
the Client to the KDC, namely Key Distribution Request.
4.  Key Distribution
This section defines how the keying material used for group
communication is distributed from the KDC to the Client, when joining
the group as a new member.
If not previously established, the Client and the KDC MUST first
establish a pairwise secure communication channel using ACE.  The
exchange of Key Distribution Request-Response MUST occur over that
secure channel.  The Client and the KDC MAY use that same secure
channel to protect further pairwise communications, that MUST be
During this exchange, the Client sends a request to the AS,
specifying the group it wishes to join (see Section 4.1).  Then, the
KDC verifies the access token and that the Client is authorized to
join that group; if so, it provides the Client with the keying
material to securely communicate with the member of the group (see
Section 4.2).
Client                                               KDC
|                                                  |
|---- Key Distribution Request: POST /group-id --->|
|<--- Key Distribution Response: 2.01 (Created) ---|
Figure 4: Message Flow of Key Distribution to a New Group Member
The same set of message can also be used for the following cases,
when the Client is already a group member:
o  The Client wishes to (re-)get the current keying material, for
cases such as expiration, loss or suspected mismatch, due to e.g.
reboot or missed group rekeying.  This is further discussed in
o  The Client wishes to (re-)get the public keys of other group
members, e.g. if it is aware of new nodes joining the group after
itself.  This is further discussed in Section 7.
Additionally, the format of the payload of the Key Distribution
Response (Section 4.2) can be reused for messages sent by the KDC to
distribute updated group keying material, in case of a new node
joining the group or of a current member leaving the group.  The key
management scheme used to send such messages could rely on, e.g.,
multicast in case of a new node joining or unicast in case of a node
leaving the group.
Note that proof-of-possession to bind the access token to the Client
is performed by using the proof-of-possession key bound to the access
token for establishing secure communication between the Client and
the KDC.
4.1.  Key Distribution Request
The Client sends a Key Distribution request to the KDC.  This
corresponds to a CoAP POST request to the endpoint in the KDC
associated to the group to join.  The endpoint in the KDC is
associated to the 'scope' value of the Authorization Request/
Response.  The payload of this request is a CBOR Map which MAY
contain the following fields, which, if included, MUST have the
corresponding values:
o  'scope', with value the specific resource that the Client is
authorized to access (i.e. group or topic identifier) and role(s),
encoded as in Section 3.1.
o  'get_pub_keys', if the Client wishes to receive the public keys of
the other nodes in the group from the KDC.  The value is an empty
CBOR Array.  This parameter may be present if the KDC stores the
public keys of the nodes in the group and distributes them to the
Client; it is useless to have here if the set of public keys of
the members of the group is known in another way, e.g. it was
provided by the AS.
o  'client_cred', with value the public key or certificate of the
Client.  If the KDC is managing (collecting from/distributing to
the Client) the public keys of the group members, this field
contains the public key of the Client.
o  'pub_keys_repos', can be present if a certificate is present in
the 'client_cred' field, with value a list of public key
repositories storing the certificate of the Client.
4.2.  Key Distribution Response
The KDC verifies the access token and, if verification succeeds,
sends a Key Distribution success Response to the Client.  This
corresponds to a 2.01 Created message.  The payload of this response
is a CBOR Map which MUST contain the following fields:
o  'key', used to send the keying material to the Client, as a
COSE_Key ([RFC8152]) containing the following parameters:
*  'kty', as defined in [RFC8152].
*  'k', as defined in [RFC8152].
*  'exp' (optionally), as defined below.  This parameter is
RECOMMENDED to be included in the COSE_Key.  If omitted, the
authorization server SHOULD provide the expiration time via
other means or document the default value.
*  'alg' (optionally), as defined in [RFC8152].
*  'kid' (optionally), as defined in [RFC8152].
*  'base iv' (optionally), as defined in [RFC8152].
*  'clientID' (optionally), as defined in
[I-D.ietf-ace-oscore-profile].
*  'serverID' (optionally), as defined in
Palombini & Tiloca       Expires April 25, 2019                [Page 10]
*  'kdf' (optionally), as defined in
*  'slt' (optionally), as defined in
*  'cs_alg' (optionally), containing the algorithm value to
countersign the message, taken from Table 5 and 6 of [RFC8152].
The parameter 'exp' identifies the expiration time in seconds after
which the COSE_Key is not valid anymore for secure communication in
the group.  A summary of 'exp' can be found in Figure 5.
+------+-------+----------------+------------+-----------------+
| Name | Label | CBOR Type      | Value      | Description     |
|      |       |                | Registry   |                 |
| exp  | TBD   | Integer or     | COSE Key   | Expiration time |
|      |       | floating-point | Common     | in seconds      |
|      |       | number         | Parameters |                 |
Figure 5: COSE Key Common Header Parameter 'exp'
Optionally, the Key Distribution Response MAY contain the following
o  'pub_keys', may only be present if 'get_pub_keys' was present in
the Key Distribution Request; this parameter is a COSE_KeySet (see
[RFC8152]), which contains the public keys of all the members of
o  'group_policies', with value a list of parameters indicating how
the group handles specific management aspects.  This includes, for
instance, approaches to achieve synchronization of sequence
numbers among group members.  The exact format of this parameter
is specific to the profile.
o  'mgt_key_material', with value the administrative keying material
to participate in the group rekeying performed by the KDC.  The
exact format and content depend on the specific rekeying scheme
used in the group, which may be specified in the profile.
Specific profiles need to specify how exactly the keying material is
used to protect the group communication.
If the application requires backward security, the KDC SHALL generate
new group keying material and securely distribute it to all the
current group members, using the message format defined in this
section.  Application profiles may define alternative message
formats.
TBD: define for verification failure
5.  Removal of a Node from the Group
This section describes at a high level how a node can be removed from
If the application requires forward security, the KDC SHALL generate
current group members but the leaving node, using the message format
defined in Section 4.2.  Application profiles may define alternative
message formats.
5.1.  Expired Authorization
If the node is not authorized anymore, the AS can directly
communicate that to the KDC.  Alternatively, the access token might
have expired.  If Token introspection is provided by the AS, the KDC
can use it as per Section 5.7 of [I-D.ietf-ace-oauth-authz], in order
to verify that the access token is still valid.
Either case, once aware that a node is not authorized anymore, the
KDC has to remove the unauthorized node from the list of group
members, if the KDC keeps track of that.
5.2.  Request to Leave the Group
A node can actively request to leave the group.  In this case, the
Client can send a request formatted as follows to the KDC, to abandon
TBD: Format of the message to leave the group
The KDC should then remove the leaving node from the list of group
Note that, after having left the group, a node may wish to join it
again.  Then, as long as the node is still authorized to join the
group, i.e. it has a still valid access token, it can re-request to
join the group directly to the KDC without needing to retrieve a new
access token from the AS.  This means that the KDC needs to keep
track of nodes with valid access tokens, before deleting all
information about the leaving node.
6.  Retrieval of Updated Keying Material
A node stops using the group keying material upon its expiration,
according to the 'exp' parameter specified in the retained COSE Key.
Then, if it wants to continue participating in the group
communication, the node has to request new updated keying material to
The Client may perform the same request to the KDC also upon
receiving messages from other group members without being able to
correctly decrypt them.  This may be due to a previous update of the
group keying material (rekeying) triggered by the KDC, that the
Client was not able to receive or decrypt.
Note that policies can be set up so that the Client sends a request
to the KDC only after a given number of unsuccessfully decrypted
incoming messages.
6.1.  Key Re-Distribution Request
To request a re-distribution of keying material, the Client sends a
shortened Key Distribution Request to the KDC (Section 4.1),
formatted as follows.  The payload MUST contain only the following
o  'scope', which contains only the identifier of the specific group
or topic, encoded as in Section 3.1.  That is, the role field is
not present.
6.2.  Key Re-Distribution Response
The KDC receiving a Key Re-Distribution Request MUST check that it is
storing a valid access token from that client for that scope.
TODO: defines error response if it does not have it / is not valid.
The KDC replies to the Client with a Key Distribution Response
containing the 'key' parameter, and optionally 'group_policies' and
'mgt_key_material', as specified in Section 4.2.  Note that this
response might simply re-provide the same keying material currently
owned by the Client, if it has not been renewed.
7.  Retrieval of Public Keys for Group Members
In case the KDC maintains the public keys of group members, a node in
the group can contact the KDC to request public keys of either all
group members or a specified subset, using the messages defined
Client                                         KDC
|                                            |
|---- Public Key Request: POST /group-id --->|
|<--- Public Key Response: 2.01 (Created) ---|
Figure 6: Message Flow of Public Key Request-Response
Note that these messages can be combined with the Key Re-Distribution
messages in Section 6, to request at the same time the keying
material and the public keys.  In this case, either a new endpoint at
the KDC may be used, or additional information needs to be sent in
the request payload, to distinguish these combined messages from the
Public Key messages described below, since they would be identical
7.1.  Public Key Request
To request public keys, the Client sends a shortened Key Distribution
Request to the KDC (Section 4.1), formatted as follows.  The payload
of this request MUST contain the following fields:
o  'get_pub_keys', which has as value a CBOR array including either:
*  no elements, i.e. an empty array, in order to request the
public key of all current group members; or
*  N elements, each of which is the identifier of a group member,
in order to request the public key of the specified nodes.
7.2.  Public Key Response
containing only the 'pub_keys' parameter, as specified in
Section 4.2.  The payload of this response contains the following
o  'pub_keys', which contains either:
*  the public keys of all the members of the group, if the
'get_pub_keys' parameter of the Public Key request was an empty
array; or
*  the public keys of the group members with the identifiers
specified in the 'get_pub_keys' parameter of the Public Key
request.
The KDC ignores possible identifiers included in the 'get_pub_keys'
parameter of the Public Key request if they are not associated to any
current group member.
The KDC must renew the group keying material upon its expiration.
The KDC should renew the keying material upon group membership
change, and should provide it to the current group members through
the rekeying scheme used in the group.
The following registration is required for the COSE Key Common
Parameter Registry specified in Section 16.5 of [RFC8152]:
o  Name: exp
o  Label: TBD
o  CBOR Type: Integer or floating-point number
o  Value Registry: COSE Key Common Parameters
o  Description: Identifies the expiration time in seconds of the COSE
o  Reference: [[this specification]]
10.  References
10.1.  Normative References
[I-D.ietf-ace-oauth-authz]
Seitz, L., Selander, G., Wahlstroem, E., Erdtman, S., and
H. Tschofenig, "Authentication and Authorization for
Constrained Environments (ACE) using the OAuth 2.0
Framework (ACE-OAuth)", draft-ietf-ace-oauth-authz-16
(work in progress), October 2018.
[I-D.ietf-ace-oauth-params]
Seitz, L., "Additional OAuth Parameters for Authorization
in Constrained Environments (ACE)", draft-ietf-ace-oauth-
params-00 (work in progress), September 2018.
[I-D.ietf-ace-oscore-profile]
Palombini, F., Seitz, L., Selander, G., and M. Gunnarsson,
"OSCORE profile of the Authentication and Authorization
for Constrained Environments Framework", draft-ietf-ace-
oscore-profile-04 (work in progress), October 2018.
[RFC8152]  Schaad, J., "CBOR Object Signing and Encryption (COSE)",
RFC 8152, DOI 10.17487/RFC8152, July 2017,
10.2.  Informative References
[I-D.ietf-core-coap-pubsub]
Koster, M., Keranen, A., and J. Jimenez, "Publish-
Subscribe Broker for the Constrained Application Protocol
(CoAP)", draft-ietf-core-coap-pubsub-05 (work in
progress), July 2018.
[RFC2093]  Harney, H. and C. Muckenhirn, "Group Key Management
Protocol (GKMP) Specification", RFC 2093,
DOI 10.17487/RFC2093, July 1997,
Protocol (GKMP) Architecture", RFC 2094,
[RFC2627]  Wallner, D., Harder, E., and R. Agee, "Key Management for
Multicast: Issues and Architectures", RFC 2627,
[RFC7390]  Rahman, A., Ed. and E. Dijk, Ed., "Group Communication for
the Constrained Application Protocol (CoAP)", RFC 7390,
The following individuals were helpful in shaping this document: Ben
Kaduk, John Mattsson, Jim Schaad, Ludwig Seitz, Goeran Selander and
Peter van der Stok.
The work on this document has been partly supported by the EIT-
Digital High Impact Initiative ACTIVE.
Francesca Palombini
Ericsson AB
Torshamnsgatan 23
Kista  SE-16440 Stockholm
Email: francesca.palombini@ericsson.com
RISE AB
Isafjordsgatan 22
Email: marco.tiloca@ri.se

redpajama_set_name: RedPajamaCommonCrawl


Whilst researching for last week's Cactus Wedding Theme Ideas feature I discovered the amazing print designer Amelie Mancini and her Etsy shop.
Amelie's patterns show her love for the botanical realm – cacti and ferns in particular. Yes, the colourful cactus is taking over the design world and you won't be able to resist the prickly prints in this collection!
These cute cactus inspired ideas would make lovely destination wedding thank you gifts and the pretty pouches would make perfect make up bags for destination brides-to-be or bridesmaids.
Do browse around the Amelie Mancini Etsy shop for yourself as there's plenty more gorgeous styles to take a peek at….


text:
package rosa.scanvas.demo.website.client.event;

import com.google.gwt.event.shared.EventHandler;

public interface PanelRequestEventHandler extends EventHandler {
	void onPanelRequest(PanelRequestEvent event);
}

redpajama_set_name: RedPajamaGithub


Those interested in seeing Touchretail in action can find us at the Autumn Fair wholesale gift and home trade show at Birmingham's NEC which runs from the 4th to the 7th of September 2016.
Chosen by leading independent retailers such as Love Aroma, Barkers Department Store, Hills Department Store and Scape Interiors, the Touchretail solution for gift and homeware retailers is ideal for omnichannel retailing. If you are looking to renew your retail system, or just starting up, we would love to show you how Touchretail can modernise your retail business. We look forward to seeing you at the NEC.


text:
Premium Ad-Free Membership
American Brands: Ford
American Brands: Chrysler
American Brands: AMC, Jeep and All Others
Automotive Histories and Misc.
Asian Brands
Australian Brands
European Brands
Cars Of A Lifetime & Auto-Biography
American Brands: GM
Trucks, Pickups and Vans
Trains, Planes & Ships
Motorcycles, Trikes, Bicycles
Engines, Transmissions and other Tech
Tractors, Lawn Mowers, Off-Road Equipment
RVs, Motorhomes, Trailers, Campers
Recent CC's & Histories
American Brands
Automotive Histories
New Car Review
Vintage Reviews
GM Brands 1950s
Ford Brands 1950s
Chrysler Brands 1950s
Other American Brands 1950s
European Brands 1950s
Asian Brands 1960s
CC Cohort
Future Semi-Classic? Toyota Rolls Out Hydrogen-Powered Tractor Unit
Ex Eugeniac
– Posted on April 23, 2017
Photo: Toyota
Toyota may soon be positioned to make two leaps in a single bound. In rolling out its hydrogen-fueled "Project Portal" tractor unit, the company expands beyond the size of existing trucks offered through its Hino brand. The impetus for leapfrogging to a trailer-hauling unit derives from Toyota's need to make the most of its investment into hydrogen fuel-cell technology for passenger cars like the finally-released-for-real Mirai. The "Portal" language stems from the unit's initially projected range of only about 200 miles in normal drayage service.
Company officials at Toyota's April 19 launch promised to use the trucks as part of a feasibility study in and around the Ports of Long Beach and Los Angeles, as well as on short hauls throughout the basin (especially to the intermodal rail yards in Vernon). Daily hauls in this type of service would be unlikely to exceed 200 miles. Operation is virtually silent; while emissions consist solely of pure H2O.
Photo: Hino Trucks
Toyota's popular and well-regarded Hino trucks are currently limited to light- and medium-duty versions (GVWs from about 15,000 to 35,000 lbs) in either conventional or cabover configurations. Typical applications include box trucks, landscaper units, bucket lift platforms, large shuttle vans, and single tankers. Brand badging on the heavy-duty (up to 80,000 GVW) "Project Portal" trucks is pointedly obscure at the moment.
Photo: Arroyo Trucking
The twin ports at LA and Long Beach now permit only Certified Clean Idle units (when diesel-powered) to make pick-ups and deliveries around the docks, almost exclusively in the form of containerized goods. The clean idle designation and accompanying sticker apply to diesel vehicles of model year 2008 or newer equipped with diesel particulate filters. Nonetheless, no idling beyond five minutes is allowed in California, including idling for sleeper berth use. In fact, even school buses must shut down within 30 seconds of arrival. Independents and small fleet operators have objected to the implementation timeline, but the rule stands [https://www.arb.ca.gov/msprog/truck-idling/factsheet.pdf]. Some exceptions apply.
Photo: John Malmin/LA Times; 1955
As part of a broader push for clean-air technologies, these vehicles and their kin have helped push down smog alerts in LA-area communities by up to 95% since the mid-1950's. In 1978, southern Californians suffered 23 days with second-stage smog alerts that called for industrial shutdowns and the suspension of after-school sports [Washington Post; Jan. 1, 1985]. Subsequent years have seen sharp reductions in Stage 1 days, while Stage 2 days have become as rare as snake toes. University of Southern California scientists note that children in the region are breathing better than they did in 1994, and that the percentage of kids with abnormally poor lung function has dropped by more than half since then [National Geographic; Mar. 4, 2015].
Photo: TFC Recycling
Other technologies, like compressed natural gas (CNG), have long been making inroads in light-to-medium duty and municipal applications. Auto drivers certainly experience far less soot, odor, and noxious emissions when following these vehicles down surface streets as they make their rounds.
A prominent reason for limiting the "Project Portal" test rigs to local runs is the fact that fuel cells and associated equipment consume most of the space that a sleeper cab would normally occupy. (Which renders somewhat fanciful Toyota's supplied cutaway image of a tractor-trailer motoring across Utah.) In Western states at least, this drawback could be potentially overcome by increasing the tractor's wheelbase, though the overall length would still count against state-imposed limits and eat into paying cargo volume. Toyota expects its hydrogen-powered trucks to be priced competitively with gasoline models if and when H2-only trucks reach the retail market. [Daily Breeze; Apr. 20, 2017]
And, judging from a quick peek at some of the advance publicity photos, it seems that sheer complexity could become an issue as miles pile up and heavy overhaul service intervals begin rearing their heads. I'm no Jimmy-jammer, and I still find even automatic transmissions to be unnecessarily complicated, but the about only things familiar to me in the above photo are a big electric motor and a fluid reservoir. Wow.
Toyota's surprise announcement came less than a week after Tesla's ever-optimistic CEO Elon Musk tweeted that his company has an electric truck set to be unveiled in September.
Musk's tweet led at least one Wall Street analyst to downgrade shares of heavy-truck maker PACCAR and diesel-engine giant Cummins, based on concerns that Tesla could emerge as a dominant player in the market for zero-emission heavy trucks. The Tesla truck would likely be battery-electric; forgoing hydrogen power for the near future at least. Still, Musk has yet to show his truck, much less explain how, when, or in what factory it would be built. Toyota has now officially fired a shot across his bow. [Motley Fool; Apr. 20, 2017].
And, just like how the butcher used to wrap up an extra bone for your dog, I thought I'd throw in this short-bed beauty for those CCer's who grew up thinking Hi-Lux!, whenever "Toyota" and "truck" were used in the same sentence.
← Car Show Classic: 1976 Oldsmobile Cutlass Supreme Brougham – The Right Car At The Right Time
Curbside Classic: 1984 Pontiac Bonneville LE – Better Than A New Volkswagen →
MikePDX
Posted April 23, 2017 at 12:35 PM
I could imagine hydrogen for long-haul trucking eventually, since it's not inconceivable for a chain of truck stops to get hydrogen refueling capability. Unlike cars, long-haul trucks call at truck stops frequently.
But 200-mile range per day for a semi tractor is surely within today's electric vehicle technology. Tesla wouldn't bother with less. Electric recharging is already widely available and would be much cheaper to install at truck stops than hydrogen refueling. As with Toyota's hydrogen car, I really don't see the point.
James Slick
Posted April 23, 2017 at 1:10 PM
Of all of the alternatives, I think battery electric is the easiest to implement., especially for urban vehicles. A battery doesn't "care" how you generate the electrical current (coal,gas,oil,nuclear,solar, Martian fairy dust…). Implementation of a voltage/amperage and connector standard seems easier than having multiple distribution systems for multiple types of fuel at the user level.
Twincamr2
I agree that battery electric is probably the most viable option, but improved charging and better energy density would be nice. I believe that will come sooner rather than later though.
Hydrogen as a fuel makes me somewhat uneasy. Aside from the fundamental problems with storage and distribution, it worries me that the momentum behind the hydrogen fuel industry is fueled by (sorry!) the desire to replicate the petrol/oil/gasoline distribution oligopoly. That's in sharp contrast to the existing, and thoroughly democratised electricity generation distribution network.
Lgbpop
Long-haul trucking? 200 miles at a clip? Sorry, that is crazy. Long-haul usually is defined in the industry as 1000 miles or more. Most diesel tractors can do that with one stop. Having to stop five times on one trip to charge up or whatever you call it makes this too time-consuming. Make it a cross-country run by a TL wildcat who has to stop 15 or 16 times between LA and New England…you'd be laughed off the road.
I can see this for strictly local-run LTL deliveries within a city or area, but long-haul…forget about it at today's level of technology development. With the increased maintenance costs, forcing this on the industry would bankrupt almost all the carriers. ABF Freight System is the only carrier I know of which HASN'T been in bankruptcy since rates were partially deregulated back in the 1980s. Getting loads terminal-to-terminal as quickly as possible is what keeps carriers operating. Keep doing everything you can to slow down transit runs, and costs will skyrocket.
That bit about long-haulers stopping frequently is a laugher. The industry is rife with stories about drivers who supposedly carried two sets of logs so they could stay on the road longer than they're allowed to by law. Tractors are most efficient when, once having gotten up to speed, they STAY at speed for as long as possible. Lastly, a tractor pulling a 30,000 lb. 53-footer takes a ton of torque to get moving, which will drain any electric vehicle batteries or H2 fuel cells like crazy.
If you "don't see the point," you've never been in the industry.
To clarify, I'm saying that I can imagine hydrogen for long-haul trucking, which I know is all day without stopping. Presumably a bigger H2 tank is cheaper than a thousand miles worth of batteries. Setting up H2 fueling at truck stops is much cheaper than H2 at every local gas station. Trucks pass by truck stops frequently and stop daily, so the refueling network would be available. The average car passes by a truck stop a lot less often, never for most.
But this "Project Portal" truck only has 200 mile range, for local work. That can certainly be handled with an electric drivetrain, probably cheaper and certainly simpler and more reliably than hydrogen. I don't see the point of a hydrogen truck with only 200 mile range.
By the way, either battery-powered or fuel-cell powered, electric motors can have tons of torque, and the torque is available from zero rpm right across the speed range. That's why locomotives use them to drive their wheels.
Jim Klein
Very interesting, thanks! For short-haul daily duties this seems good if 200 miles really is the normal round trip distance, as does Tesla's truck assuming that can be charged overnight again. A Cab-Over design would reduce the footprint back down again, it seems like everything "could" be packaged without a hood up front
Another obvious application would be school buses which pretty much drive around at defined times for predictable distances and end up parked a lot waiting for the next morning… There really is no reason for them to be belching diesel fumes and space for either the hydrogen units or batteries could easily be allocated under the floor or towards the back.
Funny you should mention school buses (I agree completely). This cartoon is in last week's New Yorker.
kiwibryce
The freight industry runs 24/7 with trucks being double shifted there is no overnite downtime for recharging, its a concept from a non industry point of view.
Paul Niedermeyer
Only a small percentage of long-haul trucks in the US are double-shifted, and almost only if it's a highly-perishable or other time-sensitive cargo . Most do stop overnight.
Julio Fernandez
I am with you Paul on the only thing recognizable under the hood being the electric motor and brake reservoir. That motor looks like the one that runs the planer at the shop I work at. It requires 600 amps on start up. I hope they have a decent battery or generator for getting up to speed on the highway or big hills.
Craig Dickson
I'm surprised you didn't mention the Nikola. It's also hydrogen fuel cell but claims an 800 to 1200 range. It supposedly will come with 1m miles of free hydrogen, and has other things like torque vectoring.
Sounds pretty interesting, but you have to wonder if it's vaporware.
https://nikolamotor.com/one
No brake fluid reservoir on trucks, they employ full air operated braking systems no fluids involved. a 200/320 km range is going to mean lots of stops for refueling compared to diesel power the clean idea is a good one, but more suited to metropolitan work than linehaul. Hino is a fairly popular Japanese truck brand here but in cabover we dont seem to have any conventionals now.
Drzhivago138
Technically speaking, air is a fluid. But we know what you meant. 😛
Thanks. Fixed.
Howard Kerr
"…..long haul trucks call at truck stops frequently."
Are you sure about that? I figured one of the things that made a "long haul" truck, long haul, was the 2 huge fuel tanks that allowed it to go several hundred miles without the need to stop. 500 to 700 miles without refueling isn't all that unheard of.
I meant daily. Thanks.
trucks are used in very different settings; some only operate extremely short distances (drayage), others in fairly short metropolitan distribution/delivery., other in regional, and others of course in long haul. So what may work readily in one setting will not so readily in another.
Electric trucks are coming for sure, and obviously the first logical settings are drayage and urban distribution/delivery. I strongly believe that batteries make more sense than fuel cells, for the same reason that they do in cars. This is an attempt to put the Mirai's fuel cell technology to some other use, as the Mira has been a total sales flop.
Hydrogen for longer haul trucks faces the same huge hurdle as it does for cars: there's no fueling infrastructure. it will be much easier to set up battery charging stations than hydrogen refueling stations.
Drastically higher-powered charging stations are on the way, which will allow charging times to drop very substantially. getting an 80% recharge in 15 minutes or less is just around the corner.
Tesla is unveiling their Tesla Semi in September. It will be very interesting to see just what approach they take. There's lots of speculation. In any case, the possibilities for shorter-medium range trucks is considerable, and the lower fuel costs are very compelling. The electrification of other transport forms will just as interesting to observe as it is in cars; for me, anyway.
The move towards more on-line shopping is creating much greater demand for regional trucking; it's the biggest area of growth. This involves lots of urban driving, congestion, etc. It is in this arena that the application of electric trucks will have their greatest early potential. Long haul trucking will undoubtedly not be so ripe for that transition for some time to come.
trucks.com covers the field very well.
Evan Reisner
I don't want to guess at these numbers (and I'm too lazy to look them up!) but I would guess that the number of highway truck stops is orders of magnitude smaller than the number of corner gas stations for cars.
It stands to reason, then, that rolling out a new fueling infrastructure (hydrogen, electricity, whatever) for long-haul trucks is orders of magnitude cheaper than doing the same for passenger cars.
I'm old enough to remember the days when owning a Diesel-powered passenger car meant the driver was mostly fueling at truck stops, because "gas stations" simply didn't have Diesel pumps.
Mouat
Looking forward to seeing how this works out. Working as a driver/dispatcher for an LTL (less than truckload=many little shipments per truck load=more revenue per load) freight transport company myself where the loads are generally lighter, I could see this application be beneficial if a longer wheelbase truck were to be necessary. This married with the allowance of spring and summer long combination vehicles of two 53, 48, or 28s in any combination (aka LCV's here in BC, Canada otherwise known as turnpike doubles/rocky mtn dbls or "21st century a-trains") and this could certainly be doable. Need more range, just use one of the trailers as a large battery or fuel or hydrogen production source.
Very interesting indeed.
Close-up of the hood emblem.
JimDandy
Wow… and the guys griped when the old manually actuated shut-down control went electric. haha
I can say that the prominently placed electric motor drives the compressor, for brake and chassis air.
Besides that and a few common truck components, I'm out.
I wonder about the drive motor(s)?
Drive through conventional final drive(s) or proprietary electric drive axles?
Both axles drive or just one?
Cab HVAC?
The steer axle looks light, very light.
Thanks, Ex, for the write up.
My pleasure. Also, in reply to kiwibryce, I suppose it might be coolant or washer fluid, or maybe super-Astro hydrojuice. But there appear to be two of them.
Its not a fluid colour I recognize sorry, and Ive recently been driving Japanese trucks Isuzus though not Hinos.
dman
Pink is the usual color of Toyota "long life" coolant, and I'm sure there's coolant recirculating somewhere in this power train. That's my guess … a coolant tank.
You're probably right, Dman.
The air compressor requires circulating liquid coolant and probably the cab's heater core too.
That's not a Toyota, that's a Kenworth 🙂 So now in addition to PACCAR, Cat and Cummins power you'll be able to get Toyota power.
Johannes Dutch
As far as I know Caterpillar stopped building diesel engines for heavy US on-highway trucks several years ago. Or are they back in business ?
Are Detroit Diesel engines available for other brands than Freightliner ? (Given the fact that Daimler owns both Detroit Diesel and Freightliner)
I remember from my old truck magazines and books that brands like Kenworth and Peterbilt had a DD, Cat or Cummins engine.
Krautwursten
Posted April 24, 2017 at 12:40 AM
Great idea for local deliveries, I'm only wondering about the weird layout occupying the space of an entire sleeper berth. Can't you simply put the hydrogen tanks in the same place where the diesel tanks would normally be? And the fuel cell inbetween the frame now that the driveshaft is gone and the electric motors sit directly at the wheels? I mean, they build fuel cell cars the size of normal cars, why not fuel cell semi trucks the size of normal semi trucks?
Click for CC's Privacy Policy
Curbside Classics Archives
American Brands:
Histories and Misc.
MAQ on Cohort Pic(k) of the Day: Jeep Compass Hearse – Yes, Your Read That Right
Mark on Curbside Classic: 1962-67 S40 Toyota Crown – The Generation Gap
wigwam on Cohort Pic(k) of the Day: Jeep Compass Hearse – Yes, Your Read That Right
George Ferencz on Flookerang Funnies: One Fine Day in a Detroit Office
Paul Niedermeyer on CC Library: Reading "God's Own Junkyard" 58 Years Later
Norm on CC Library: Reading "God's Own Junkyard" 58 Years Later
LostDog on 1995 – 2000 Toyota Cavalier – GM Tries To Invade The Japanese Market With A Little Help
rudiger on Flookerang Funnies: One Fine Day in a Detroit Office
210delray on CC Library: Reading "God's Own Junkyard" 58 Years Later
Copyright 2011 - 2021 Curbside Classics. All Rights Reserved.


Thoughts and actions are intimately linked, and the mere thought of an action is much like actually performing it. The brain prepares for an action by generating a motor simulation of it, praticising its execution of the movements by going through the motions invisibly. Seeing a manipulable object such as a tool, for example, automatically triggers a simulation of using it - a mental image of reaching out and grasping it with the hand that is nearest to the handle.
Motor simulations and movements are known to influence thought processes. Magnetic stimulation of the motor cortex influences the processing of words related to arm and leg action, whereas polonged movements in one direction slow the comprehension of sentences related to movements in the other. Psychologist Jessica Witt of the Action-Modulated Perception Laboratory at Purdue University and her colleagues now provide further evidence of this link - in a study published online in the journal Psychological Science, they show that motor simulations may enhance the recognition of tools.


text:
Glorious India
Visit this wonderful ancient land
India: an overview
National Animal
National Emblem
National Flower
National Fruit
National Tree
Culture of India
Ancient Indian History
Indian Architecture
Indian Sculpture
Indian Philosophy
Indian Epics
Religions of India
People of India
C.V. Raman
Har Gobind Khurana
Subramaniam Chandrashekhar
Religious Teachers
Sant Kabir
Trailanga Swami
Vardhaman Mahavira
Hindu Trinity
The Preserver
Cosmic Trinity
Lesser Gods
Seshnag
Airavata
Trailanga Swami (also Tailang Swami, Telang Swami) (reportedly 1607 – 1887) was a Hindu yogi famed for his spiritual powers who lived in Varanasi, India. He is regarded as a legendary figure in Bengal, with many stories told about his yogic powers and longevity. According to some accounts, Trailanga Swami lived to be 280 years old, residing at Varanasi between 1737-1887. He is regarded by devotees as an incarnation of Shiva. Ramakrishna referred to him as the "The walking Shiva of Varanasi".
A member of the Dashanami order, he became known as Trailanga Swami after he settled in Varanasi. His biographers and his disciples differ on his birth date and the period of his longevity. According to one disciple biographer, he was born in 1529, while according to another biographer it was 1607. His pre-monastic name was Shivarama and was born in Holia at Vizianagaram in Andhra Pradesh. His parents were Narashingha Rao and Vidyavati Devi, who were devotees of god Shiva. After the death of his parents, at the age of forty, he was said to have renounced the world and lived the life of a recluse in a cottage near a cremation ground. After practicing sadhana (spiritual practice) for twenty years, he met his preceptor swami, Bhagirathananda Saraswati, in 1679 from Punjab. Bhagirathananda initiated Shivaram into sannyasa (monastic vows) and named him Swami Ganapati Saraswati in 1685. Ganapati reportedly led a life of severe austerities and went on a pilgrimage, reaching Prayag in 1733, and finally settling in Varanasi in 1737.
In Varanasi, till his death in 1887, he lived at different places including Asi Ghat, the Vedavyas Asharama at Hanuman Ghat, Dashashwamedh Ghat. He was often found roaming the streets or the ghats, naked and "carefree as a child". He was reportedly seen swimming or floating on Ganges for hours. He talked very little and at times not at all. A large number of people became attracted to him upon hearing of his yogic powers to ameliorate their sufferings. During his stay in Varanasi, several prominent contemporary Bengalis known as saints met and described him, including Ramakrishna, Vivekananda, Mahendranath Gupta, Lahiri Mahasaya, and Swami Abhedananda., Swami Bhaskarananda Saraswati, Vishuddhananda Saraswati, and Mahatma Vijaykrishna Goswami. After seeing Trailanga Swami, Ramakrishna said, "I saw that the universal Lord Himself was using his body as a vehicle for manifestation. He was in an exalted state of knowledge. There was no body-consciousness in him. Sand there became so hot in the sun that no one could set foot on it. But he lay comfortably on it." Ramakrishna also stated that Trailanga Swami was a real paramahansa (lit:"Supreme swan", used as an honorific for a spiritual teacher) and that "all Benares was illuminated by his stay there."
The Swami had taken the vow of ayachaka (non seeking) — remaining satisfied with whatever he received. In the later stage of his life, as his fame spread, pilgrims visited him in multitudes. During his last days, he took up ajagaravritti (living like a python) in which he sat still without any movement, and devotees poured water (abhisheka) on him from early morning till noon, looking upon him as a living incarnation of Shiva. He died on Monday evening, December 26, 1887. His body was given salilasamadhi in the Ganges river, according to the funeral customs of the monks of the Dashanami sect, in the presence of a multitude of mourning devotees standing on the ghats.
Legends and Stories
There are many stories told about Telang Swami and his spiritual powers, such that he has become a nearly mythical figure in India. Robert Arnett writes that Telang Swami's miracles are "well documented" and "he displayed miraculous powers that cannot be dismissed as myth" and there were living witnesses to his "amazing feats". He was reputed to have lived to be around 300 years, and was a larger than life figure, reportedly weighing over 300 pounds (140 kg), though he seldom ate. One account said that he could "read people's minds like books."
On many occasions, he was seen to drink deadly poisons with no ill effect. In one instance, a skeptic wanted to expose him as a fraud. The monk was accustomed to breaking his long fasts with buckets of clabbered milk, so the skeptic brought him a bucket of calcium-lime mixture used for whitewashing walls instead. The monk drank the entire bucket with no ill effect — instead, the skeptic fell to the ground writhing in pain. The monk broke his usual silence to explain the law of karma, of cause and effect.
According to another story, he often walked around without any clothes, much like the naga (or "sky-clad") sadhus. The Varanasi police were scandalized by his behaviour, and had him locked in a jail cell. He was soon seen on the prison roof, in all his 'sky-clad' glory. The police put him back into his locked cell, only to see him appear again on the jail roof. They soon gave up, and let him again walk the streets of Varanasi.
Thousands of people reportedly saw him levitating in a sitting position on the surface of the river Ganges for days at a time. He would also apparently disappear under the waves for long periods, and reappear unharmed. Swami Sivananda attributed some of his miracles to the siddhi or yogic power Bhutajaya — conquest over the five elements, "Fire will not burn such a Yogi. Water will not drown him."
With respect to his reportedly yogic powers, miracles abundant in his biographies and exceptionally long life, Swami Medhasananda writes that according to the "science of yoga", attainment of these is not "impossible".
His teachings are extant and are available in a biography by Umacharan Mukhopadhyay, one of his disciples. He described bondage as "attachment to the world" and liberation as "renunciation of the world and absorption in God." He further said that after attaining the state of desirelessness, "this world is transformed into heaven" and one can be liberated from samsara (the Hindu belief that life is a cycle of birth and death) through "spiritual knowledge". He remarks that attachment to the "evanescent" world is "our chronic disease" and the medicine is "detachment".
He described man's senses as his enemy and his controlled senses as his friend. His description of a poor person as one who is "very greedy" and regarded one who always remains content as rich. He said that the greatest place of pilgrimage is "Our own pure mind" and instructs to follow the "Vedantic truth from the Guru." He described a sadhu as one who is free from attachment and delusion.
Muharram September 20, 2018
Maha Shivaratri February 12, 2018
Republic Day January 26, 2018
Khandvi June 19, 2015
Gobi Manchurian June 9, 2015
Culture of India (15)
Hindu Trinity (1)
Hinduism Festivals (5)
Indian Festivals (8)
Muslim Festivals (1)
Mythological Stories (2)
Recipes of India (2)
States (12)
andaman and nicobar asiatic lion assam assam rhino assam tea basant panchami bihu brahma culture of india deepawali diwali durga puja dussehra festival of colors festival of india ganesha chaturthi gir national park goa gujarat hindu festival hindu festivals hindu trinity holi indian epics indian festival indian mythology indian painting indian philosophy indian sculpture jharkhand kaziranga kolkata mahabharata navaratri north east corridor panaji ramayana saraswati puja shiva state of india states of india the creator uttarakhand vishnu west bengal
Copyright © 2020. Glorious India. Powered by iSoftLogix.


We're happy to confirm that this afternoon's matinee performance of salt. is going ahead as scheduled! If you had a ticket to Friday or Saturday night's performances that you have not yet exchanged or had refunded, please email tickets@pushfestival.ca or call 604.449.6000. (from 10am). Thank you to everyone for their patience and kindness with this process — we are so grateful to our audiences for their understanding!
Note: This performance features the use of incense.
WRITER, PERFORMER Selina Thompson DIRECTOR Dawn Walton DESIGNER Katherina Radeva LIGHTING DESIGNER Cassie Mitchell RELIGHTS Louise Gregory SOUND DESIGNER Sleepdogs Collective DRAMATURGICAL SUPPORT Maddy Costa, Season Butler & Bryony Kimmings PRODUCER Emma Beverley PRODUCTION MANAGER Louise Gregory PHOTOGRAPHER, DOCUMENTER Richard Davenport COMMISSIONED BY Yorkshire Festival, Theatre Bristol and MAYK SUPPORTED BY Arts Council England and 200 kind and generous supporters who donated towards the voyage across the Atlantic.


TEAMDEVELOPER TIPS & TRICKS MAKES NO GUARANTEE OF VALIDITY
 Team Developer Tips & Tricks is an online open-content collaborative encyclopedia, that is, a voluntary association of individuals and groups working to develop a common resource of human knowledge. The structure of the project allows anyone with an Internet connection to alter its content. Please be advised that nothing found here has necessarily been reviewed by people with the expertise required to provide you with complete, accurate or reliable information. That is not to say that you will not find valuable and accurate information; much of the time you will. However, '''Team Developer Tips & Tricks Wiki cannot guarantee the validity of the information found here.''' The content of any given article may recently have been changed, vandalized or altered by someone whose opinion does not correspond with the state of knowledge in the relevant fields. === No formal peer review === We are working on ways to select and highlight reliable versions of articles. However, information here is not uniformly peer reviewed; while readers may correct errors, they have no legal duty to do so and thus all information read here is without any implied warranty of fitness for any purpose or use whatsoever. Even articles that have been vetted by informal peer review or articles processes may later have been edited inappropriately, just before you view them. '''None of the contributors, sponsors, administrators, or anyone else connected with Team Developer Tips & Tricks Wiki in any way whatsoever can be responsible for the appearance of any inaccurate or libelous information or for your use of the information contained in or linked from these web pages.''' === No contract; limited license === Please make sure that you understand that the information provided here is being provided freely, and that no kind of agreement or contract is created between you and the owners or users of this site, the owners of the servers upon which it is housed, the individual contributors, any project administrators, sysops or anyone else who is in ''any way connected'' with this project or sister projects subject to your claims against them directly. You are being granted a limited license to copy anything from this site; it does not create or imply any contractual or extracontractual liability on the part of Team Developer Tips & Tricks Wiki or any of its agents, members, organizers or other users. There is '''no agreement or understanding between you and Team Developer Tips & Tricks Wiki''' regarding your use or modification of this information beyond the [[GNU Free Documentation License]] (GFDL); neither is anyone at Team Developer Tips & Tricks Wiki responsible should someone change, edit, modify or remove any information that you may post on Team Developer Tips & Tricks Wiki or any of its associated projects. === Trademarks === Any of the trademarks, service marks, collective marks, design rights, personality rights or similar rights that are mentioned, used or cited in the articles of Team Developer Tips & Tricks Wiki are the property of their respective owners. Their use here does not imply that you may use them for any other purpose other than for the same or a similar informational use as contemplated by the original authors of these Team Developer Tips & Tricks Wiki articles under the GFDL licensing scheme. Unless otherwise stated Team Developer Tips & Tricks Wiki sites are neither endorsed nor affiliated with any of the holders of any such rights and as such Team Developer Tips & Tricks Wiki cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk. === Jurisdiction and legality of content === Publication of information found in Team Developer Tips & Tricks Wiki may be in violation of the laws of the country or jurisdiction from where you are viewing this information. Laws in your country or jurisdiction may not protect or allow the same kinds of speech or distribution. Team Developer Tips & Tricks Wiki does not encourage the violation of any laws; and cannot be responsible for any violations of such laws, should you link to this domain or use, reproduce, or republish the information contained herein. === Not professional advice === If you need specific advice please seek a professional who is licensed or knowledgeable in that area.
Return to Team Developer SqlWindows Wiki:General disclaimer.


text:
class Api::BaseController < ActionController::Base
  class ScopeNotHandled < StandardError; end
  class RegistryNotHandled < StandardError; end
  class WrongPortusOTP < StandardError; end

  include Pundit

  respond_to :json

  rescue_from Namespace::AuthScope::ResourceIsNotFound, with: :deny_access
  rescue_from Pundit::NotAuthorizedError, with: :deny_access
  rescue_from ScopeNotHandled, with: :deny_access
  rescue_from RegistryNotHandled, with: :deny_access
  rescue_from WrongPortusOTP, with: :deny_access

  protected

  def deny_access
    head :unauthorized
  end

  def scope_handler(registry, scope_string)
    type = scope_string.split(":", 3)[0]

    case type
    when "repository"
      auth_scope = Namespace::AuthScope.new(registry, scope_string)
    else
      logger.error "Scope not handled: #{type}"
      raise ScopeNotHandled
    end

    scopes = scope_string.split(":", 3)[2].split(",")

    [auth_scope, scopes]
  end
end


text:
Q: In AngularJS, is there a way to know that there is duplicate in the data.location, and only output once for each unique data.location In AngularJS, is there a way to know that there is duplicate in the data.location, and only output once for each unique data.location.
I.e.  Instead of the following:
   A    Jane
   A    Tom
   B    Brian
   B    Jane
   B    Mike
   R    Donald
   R    Jerry

would prefer expected output to be:
   A    Jane
        Tom
   B    Brian
        Jane
        Mike
   R    Donald
        Jerry

The angular code as follows:

redpajama_set_name: RedPajamaStackExchange


text:
Q: Set array element using another array containing path I have an array like
$arr = [
  'foo' => [
    'bar' => [
      1
    ],
    'baz' => [
      1
    ]
  ]
]

And another one
$path = ['foo', 'bar', 0];

I need to modify the value from $arr using $path. I need the solution to be very simple, I tried something like
$arr...$path = 2;
$arr[...$path] = 2;

After the modification $arr should look like
$arr = [
  'foo' => [
    'bar' => [
      2
    ],
    'baz' => [
      1
    ]
  ]
]

But I got errors. I don't always know how many levels the array will have.

A: Your path is incorrect -  for $arr[$path] = 2; you need
$path = ['foo', 'bar', 0];

$p = &$arr;
foreach($path as $step)
   $p = &$p[$step];
echo $p . "\n";
$p = 2;
print_r($arr);

Or with
$path = ['foo', 'bar'];

$p = &$arr;
foreach($path as $step)
   $p = &$p[$step];
echo $p[0] . "\n";
$p[0] = 2;
print_r($arr);

A: Try this:
$link =& $arr;
foreach ($path AS $p)
{
    $link =& $link[$p];
}
$link[0]++;

A: $arr[$path[0]][$path[1]] ='XXX'


The end of the year is only a few days away. For business owners, this is the best time to review your annual success and growth and make the necessary plans for 2019. It is also important to consider refreshing your website content with a Pro Copywriter for the New Year to experience greater business success.
A web copy or web content refers to everything that visitors can see on your website. This varies from website to website but mostly includes web pages, images, blog posts, products and descriptions, and so on. Here are the top reasons why refreshing your web copy is vital for business success in 2019.
For your website to come up in organic searches and be made visible to visitors or potential customers, the search engines like Google must perform what is known as indexing. When you don't add fresh content to your website, your search engine ranking position falls over time. Hence, to stay visible in 2019, it is necessary to refresh your web copy for SEO.
Websites are built every day, and 2019 will guarantee that you have even more competitors in the online market. To maintain relevance and keep your customers, you must establish your brand authority with fresh content. It proves you are updated and an expert in that niche. It also reminds your customers that you are still in business.
The New Year will bring with it the latest trends and updates. It is not news that the digital market and your customers are dynamic. Their needs, methods, products, and others are constantly changing. Refreshing your website content will give you the chance to tap into any trends and guarantee business success for 2019.
Refreshing your web copy is not an easy task and should not be taken lightly either. Regardless of if you need to add or re-write content, you would require a professional copywriter.
A copywriter knows exactly what is at stake in the New Year and is already informed on trends and updates in the market. They know how to present your brand and set it up with content for business success in 2019.
A pro copywriter knows how and where to place important keywords for optimum visibility and SEO.
Hiring a pro copywriter allows you to use their experience with competitors and other niches to provide you with quality, relevant content. It guarantees that you can truly experience the benefits of fresh website content.


Set the source dir to find the files to be renamed.
from - the extension of files being renamed.
to - the extension of the renamed files.
replace - if true overwrite any target files that exist.
srcDir - the source directory.
BuildException - is there is a problem in the task execution.


text:
Q: Fitting power-law distributions with poweRlaw package in R With poweRlaw library, and once computed alpha and xmin with estimate_xmin, which formula the script uses to compute the fitted values?
I mean, assuming that y=C·x^(-alpha), my question is how the script computes the normalization constant from alpha and xmin.

A: The normalising constant is fairly easy to calculate. See the Clauset et al's powerlaw paper (in particular table 2.1). For the continuous case, C = (alpha-1) xmin^(alpha-1), the discrete case involves calculating the diagamma function.
You can also examine the R code:

*

*Discrete

*Continuous


text:
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace LaharlCSharp.BreakLines
{
	internal class BreakableNode : Node
	{
		internal IList<Node> Children { get; set; }

		internal override string UnbrokenText
		{
			get
			{
				var builder = new StringBuilder();
				foreach (var node in Children)
				{
					if (node.PrecededBySpaceWhenUnbroken)
						builder.Append(" ");
					builder.Append(node.UnbrokenText);
				}
				return builder.ToString();
			}
		}
	}
}


What do you think about Ceiling Fans For Bedrooms Best ?
It's interested and make you have an idea to design your room? Get your idea with picture from Ceiling Fans For Bedrooms Best, If you inspiration dont forget to email or contact us when you're happy. Ceiling Fans For Bedrooms Best was posted in August 21, 2016 at 1:20 pm and This Ceiling Fans For Bedrooms Best has viewed by 138 users. Browse all of Christmas 2018. You may found another Ceiling Fans For Bedrooms Best better design ideas.


text:
Sign up for the Daily Digest E-mail
Well Activity Map
M&A Activity
AER Transfers
Rig Counts
CAODC Rig Count
Baker Hughes Rig Count
USA Rig Count
Canada Well Licences
USA Market Data
Data Subscription
Kinder Morgan Canada Limited Declares Dividend and Announces Results for Fourth Quarter of 2018
January 16, 2019 2:05 PM CNW
Restricted Voting Shareholders Receive $1.2 Billion Return of Capital Distributions
CALGARY, Jan. 16, 2019 /CNW/ – The Kinder Morgan Canada Limited (TSX: KML) board of directors has declared a dividend for the fourth quarter of 2018 of $0.1625 per split-adjusted restricted voting share ($0.65 annualized), payable on February 15, 2019, to restricted voting shareholders of record as of January 31, 2019. KML's restricted voting share dividends are eligible dividends for Canadian income tax purposes. KML's board also determined to suspend KML's dividend reinvestment plan (DRIP), effective with this dividend in light of KML's reduced need for capital.
"KML's strategic infrastructure operations across western Canada had a strong fourth quarter, underpinned by multi-year take-or-pay contracts with high quality customers and stable cash flows," said KML Board Chairman and CEO Steve Kean. "As we have said previously, the original purpose of KML was to hold a strong set of midstream assets and to provide a funding mechanism for the Trans Mountain expansion," said Dax Sanders, KML Chief Financial Officer. "In light of last year's Trans Mountain sale, KML continues to evaluate all options in order to maximize value to KML shareholders. Those options include, among others, continuing to operate as a standalone enterprise, a disposition by sale, or a strategic combination with another company."
KML reported fourth quarter income from continuing operations of $40.3 million, an increase of $22.3 million from the fourth quarter of 2017. Distributable cash flow (DCF) from continuing operations was $62.9 million, up 84 percent compared to the comparable prior year period. DCF from continuing operations for the quarter benefited from interest income on the deposited proceeds from the sale of Trans Mountain as well as greater contributions from both the Pipelines and Terminals segments versus the same period in 2017, partially offset by a full quarter of Series 3 preferred stock dividends in 2018.
In the fourth quarter, KML generated earnings per split-adjusted restricted voting share from continuing operations of $0.30. KML produced DCF from continuing operations of $0.53 per split-adjusted restricted voting share relative to our declared $0.1625 per split-adjusted restricted voting share dividend, resulting in $12.8 million of excess DCF coverage above the company's dividend.
Overview of Business Segments
"Earnings in our Terminals segment were up 13 percent compared to the fourth quarter of 2017. At our Edmonton-area terminals, volume was up 5.6 million barrels, or 19 percent, year-over-year, driven by the new Base Line Terminal joint venture coming online and strong demand for rail loadings at Edmonton South Rail Terminal and Alberta Crude Terminal," noted John Schlosser, KML President. "Contributions from Base Line Terminal and higher rates achieved on re-contracted tank leases at our North 40 and Edmonton South terminals were partially offset by a $6.1 million true-up in terminal fees in connection with a favorable arbitration ruling recognized in the prior year period.
"Contributions from our Vancouver Wharves facility were up nearly 10 percent compared to the fourth quarter of 2017 driven by strong distillate volumes and fees associated with a project to re-activate an idled mineral concentrate storage shed," continued Schlosser.
"Pipeline segment earnings were up 39 percent compared to the fourth quarter of 2017, led by Cochin. Cochin's increased earnings were primarily due to timing on the recognition of deficiency revenue."
Return of Capital Distributions and Share Consolidation
Approximately $3,977.4 million of the proceeds from the August 31, 2018 sale of the Trans Mountain pipeline system were disbursed to KML's voting shareholders on January 3, 2019, including approximately $1,195.1 million distributed to KML's restricted voting shareholders as a return of capital ($11.40 per share). On January 4, 2019, KML effected a "reverse stock split" of its restricted voting shares and special voting shares on a one-for-three basis (three shares consolidating to one share). Also during the fourth quarter, KML received shareholder approval and recorded a reduction of its stated capital of KML's restricted voting shares by $1.45 billion. The above transactions had no impact on KML's outstanding preferred shares or dividends payable thereon.
For 2019, as previously disclosed, KML's budget contemplates declaring a dividend of $0.65 per restricted voting share, generating Adjusted EBITDA of $213 million and DCF from continuing operations of approximately $109 million, representing DCF of $0.90 per split-adjusted restricted voting share. KML's budget also contemplates investing approximately $32 million in expansion projects, and ending the year with a Net Debt-to-Adjusted EBITDA ratio of approximately 1.3 times (treating 50 percent of the outstanding preferred equity balance as debt).
We do not provide forecasted income from continuing operations (the GAAP financial measure most directly comparable to the non-GAAP financial measures DCF from continuing operations and Adjusted EBITDA) due to the impracticality of quantifying certain amounts required by GAAP, such as realized and unrealized foreign currency gains and losses and potential changes in estimates for certain contingent liabilities.
KML's board of directors declared a dividend of $0.328125 per Series 1 preferred share ($1.3125 annualized) and $0.3250 per Series 3 preferred share ($1.30 annualized), each payable on February 15, 2019 to Series 1 and Series 3 preferred shareholders of record as of the close of business on January 31, 2019. KML's preferred share dividends are eligible dividends for Canadian income tax purposes.
As noted above, KML's board of directors has also suspended, until further notice, KML's DRIP, effective January 16, 2019. Accordingly, dividends in respect of the fourth quarter of 2018, payable on February 15, 2019 to holders of restricted voting shares of record as of the close of business on January 31, 2019, will not be reinvested through the DRIP. Shareholders who were enrolled in the program will automatically receive dividend payments in the form of cash. If KML elects to reinstate the DRIP in the future, shareholders who were enrolled in the DRIP at suspension and remained enrolled at reinstatement will automatically resume participation in the DRIP. Kinder Morgan, Inc.'s participation in the distribution reinvestment in Class B units of Kinder Morgan Canada Limited Partnership has been suspended since July 18, 2018.
With the final tanks placed in service early in the fourth quarter of 2018, construction of all major facilities at the Base Line Terminal in Edmonton, Alberta, Canada, is complete. The 12-tank, 4.8 million barrel facility is fully contracted with long-term, firm take-or-pay agreements with creditworthy customers. The 50-50 joint venture crude oil merchant storage terminal developed by KML and Keyera Corp. was completed on time and under budget, with Kinder Morgan investing approximately $357 million.
Permitting efforts continue on the distillate storage expansion project at KML's Vancouver Wharves terminal in North Vancouver, British Columbia. The $43 million capital project includes the construction of two new distillate tanks with combined storage capacity of 200,000 barrels and enhancements to the railcar unloading capabilities. The project is supported by a 20-year initial term, take-or-pay contract with an affiliate of a large, international integrated energy company and is expected to be placed in service in the first quarter of 2021.
About Kinder Morgan Canada Limited (TSX: KML). KML manages and is the holder of an approximately 30 percent minority interest in a portfolio of strategic energy infrastructure assets across Western Canada. Kinder Morgan, Inc. (NYSE: KMI) holds an approximately 70 percent majority voting interest in KML and a corresponding 70 percent economic interest in KML's business and assets. KML focuses on stable, fee-based energy transportation and storage assets that are central to the energy infrastructure of Western Canada. We strive to promote shareholder value by increasing utilization of our existing assets while controlling costs and operating in a safe and environmentally responsible way. For more information visit kindermorgancanadalimited.com
Kinder Morgan Canada Limited and Subsidiaries
Preliminary Consolidated Statements of Income
(In millions of Canadian dollars, except per share amounts)
Costs, expenses and other
Taxes, other than income taxes
Other (income) expense, net
Interest, net
Foreign exchange loss
(Loss) Income from Discontinued Operations, net of tax (1)
Preferred share dividends
Net income attributable to KMI interest
Net income available to restricted voting stockholders
Restricted Voting Shares
Basic and diluted earnings per restricted voting share from Continuing Operations
Basic and diluted earnings per restricted voting share from Discontinued Operations (1)
Basic and diluted weighted average restricted voting shares outstanding (2)
Segment EBDA
Total Segment EBDA from Continuing Operations
Represents income from TMPL and TMEP and related assets, including a gain of $1,280.2 million, net of tax, for 2018.
Reflects our Jan. 2019 1-for-3 reverse stock split for all periods presented in accordance with U.S. GAAP.
Preliminary Earnings Contribution by Business Segment
Twelve Months
Ended December 31,
Segment EBDA before certain items (1)
DD&A
General and administrative and corporate charges (1)
Interest income (expense), net (1) (2)
Book taxes (1)
Income from continuing operations before Certain Items ("Adjusted Earnings from continuing operations")
Certain items
Foreign exchange loss on the KMI Loans
Gain on divestitures, net
Subtotal certain items before tax
Book tax certain items
Total certain items
Income from discontinued operations (3)
Continuing Operations:
Adjusted earnings from continuing operations
Total book taxes
Cash taxes
Sustaining capital expenditures
DCF from continuing operations
DCF from continuing operations to KMI interest
DCF from continuing operations for restricted voting stockholders (4)
Weighted average split-adjusted restricted voting shares outstanding for dividends (5)
DCF from continuing operations per split-adjusted restricted voting share
Adjusted EBITDA from continuing operations (6)
Notes (In millions of Canadian dollars)
Excludes certain items:
4Q 2018 – Terminals $0.1, general and administrative $(4.1), book tax $1.2
4Q 2017 – General and administrative $(0.2)
YTD 2018 – Terminals $9.6, general and administrative $(5.5), interest expense $(1.0), book tax $(0.9)
YTD 2017 – General and administrative $(2.8), book tax $0.7
For the periods prior to our May 30, 2017 initial public offering, amounts were associated with KMI loans that were repaid 2Q 2017.
Includes the gain on sale of Trans Mountain, net of tax, for 4Q 2018 and YTD 2018 of $(27.8) and $1,280.2, respectively.
DCF is calculated as follows:
(Loss) Income from discontinued operations, net of tax
Certain items before book tax (3)
(1,131.2)
Book tax certain items (3)
Total book taxes before certain items
DCF from discontinued operations
DCF from continuing operations for restricted voting stockholders
Reflects our Jan. 2019 1-for-3 reverse stock split for all periods presented in accordance with U.S. GAAP. Also, includes stock awards of restricted voting shares that participate in dividends. The 2017 weighted average restricted voting shares outstanding for dividends calculation is based on the actual days in which the shares were outstanding for the period from May 30, 2017 to June 30, 2017. Therefore, the amounts differ from the GAAP weighted average restricted voting shares outstanding from the date of our formation.
Adjusted EBITDA is calculated as follows:
Interest, net before certain items
Adjusted EBITDA from discontinued operations
Adjusted EBITDA from continuing operations
Volume Highlights
(Historical pro forma for acquired assets)
Liquids Leasable Capacity (MMBbl) (1)
Liquids Utilization %
Bulk Transload Tonnage (MMtons)
Canadian Cochin (MBbl/d – mainline throughput)
Includes KML's share of Joint Venture capacity.
Preliminary Consolidated Balance Sheets
(In millions of Canadian dollars)
Current assets held for sale (1)
Long-term assets held for sale (1)
Deferred charges and other assets
LIABILITIES AND EQUITY
Current liabilities held for sale (1)
Distribution payable
Distribution payable-related parties
Other current liabilities (2)
Long-term liabilities held for sale (1)
Other long-term liabilities (2)
Other equity
Total KML equity
KMI interest
TOTAL LIABILITIES AND EQUITY
Net Debt (Cash)
Net Debt (Cash) including 50% of KML preferred shares (3)
Reconciliation of Net Income to Adjusted EBITDA
Adjusted EBITDA (4)
Net Debt (Cash) including 50% of KML preferred shares to Adjusted EBITDA
Amounts related to Trans Mountain are presented as held for sale as of December 31, 2017 in accordance with GAAP. These assets and liabilities were not actually being held for sale at that point in time.
Includes impact to accrued taxes and deferred income taxes resulting from the sale of Trans Mountain pipeline system.
December 31, 2018 and 2017 amounts include: $275 million representing 50% of our preferred stock, which is included in Other equity. 2018 excludes Return of Capital dividends of $3,977.4 million.
Includes both continuing operations and discontinued operations, see Note (6) to Preliminary Earnings Contribution by Business Segment page.
Advisories & Contact
Please join KMI and KML at 4:30 p.m Eastern Time on Wednesday, January 16, 2019, at www.kindermorgan.com for a LIVE webcast conference call that will include a discussion of KML's third quarter earnings.
Important Information Relating to Forward-Looking Statements
This news release includes "forward-looking information," "financial outlook," and "forward-looking statements" within the meaning of applicable securities laws (forward-looking statements). Forward-looking statements in this news release include statements, express or implied, concerning, without limitation: KML's expected Adjusted EBITDA and DCF for 2019 and expected Adjusted EBITDA to debt at the end of 2019; and anticipated dividends and the intended payment thereof. Forward-looking statements are not guarantees of performance. They involve significant risks, uncertainties and assumptions. Any financial outlook or other forward-looking statements provided in this news release have been included for the purpose of providing information relating to management's current expectations and plans for the future, are based on a number of significant assumptions and may not be appropriate, and should not be used, for any other purpose. Future actions, conditions or events and future results of operations may differ materially from those expressed in forward-looking statements. Many of the factors that will determine these results, including the ability of KML to pay dividends, are beyond the ability of KML to control or predict. As noted above, the forward-looking statements in this release are based on a number of material assumptions, including among others those discussed in this news release or inherent in the factors highlighted below. Among other things, specific factors that could cause actual results to differ from those indicated in the forward-looking statements provided in this news release include, without limitation: changes in demand for KML's services; issues, delays or stoppages associated with major expansion projects; significant unanticipated cost increases or required capital expenditures; the breakdown or failure of equipment, pipelines and facilities, releases or spills, operational disruptions or service interruptions; the ability of KML's counterparties to perform; the ability of KML to access sufficient external sources of financing, and the cost of such financing; and changes in the regulatory environment.
The foregoing list should not be construed to be exhaustive. In addition to the foregoing, important additional information respecting the material assumptions, expectations and risks applicable to forward-looking statements included in this news release are set out in KML's press release dated December 3, 2018 regarding financial expectations for 2019 and KML's Annual Report on Form 10-K for the year-ended December 31, 2017 (under the headings "Risk Factors," "Information Regarding Forward-Looking Statements," "Management's Discussion and Analysis of Financial Condition and Results of Operations" and elsewhere) and KML's subsequent reports, which are available through the SEC's EDGAR system at www.sec.gov, under KML's profile on SEDAR at www.sedar.com and on KML's website at ir.kindermorgancanadalimited.com. Shareholders and prospective investors are urged to review and carefully consider such information prior to making any investment decision in respect of KML's restricted voting shares. The risk factors applicable to KML could cause actual results to vary materially from those contained in any forward-looking statements. KML disclaims any obligation, other than as required by applicable law, to update the forward-looking statements included in this release.
Non-GAAP Financial Measures
KML's financial information has been prepared in accordance with United States generally accepted accounting principles (GAAP). In addition to using measures prescribed by GAAP, this news release includes references to DCF (both in the aggregate and per share), net income before interest expense, taxes, depreciation, depletion and amortization (DD&A) and adjusted for Certain Items (Adjusted EBITDA), segment earnings before DD&A and Certain Items (Segment EBDA before Certain Items) and Adjusted Earnings, all of which are financial measures that do not have any standardized meaning as prescribed by GAAP (non-GAAP measures). DCF, Adjusted EBITDA, Segment EBDA before Certain Items and Adjusted Earnings should not be considered alternatives to GAAP net cash provided by operating activities, net income or Segment EBDA, respectively, computed under GAAP or any other GAAP measures, and such non-GAAP measures have important limitations as analytical tools. The computations of DCF, Adjusted EBITDA, Segment EBDA before Certain Items and Adjusted Earnings may differ from similarly titled measures used by others. Accordingly the use of such terms may not be comparable to similarly defined measures presented by other entities and investors should not consider these non-GAAP measures in isolation or as a substitute for an analysis of results reported under GAAP. Management compensates for the limitations of these non-GAAP measures by reviewing our comparable GAAP measures, understanding the differences between the measures and taking this information into account in its analysis and its decision-making processes.
Discontinued Operations are included in our non-GAAP measures in the accompanying tables for the 2017 periods and the period from January 1, 2018 to the close of the Trans Mountain transaction on August 31, 2018. The non-GAAP measures, DCF from discontinued operations and Adjusted EBITDA from discontinued operations, are reconciled to income from discontinued operations, the most directly comparable GAAP measure, in notes (4) and (6) to the Preliminary Earnings Contribution by Business Segment tables.
Non-GAAP measures from continuing operations reflect our ongoing operations and have been presented as DCF from continuing operations, Adjusted EBITDA from continuing operations and Adjusted Earnings from continuing operations. In addition, DCF per restricted voting share presented herein reflects our January 4, 2019 one-for-three reverse stock split and is presented as DCF from continuing operations per split-adjusted restricted voting share for all periods presented. The most comparable GAAP measure to the above non-GAAP measures from continuing operations is income from continuing operations and the accompanying tables and notes thereto include reconciliations of the above non-GAAP measures to income from continuing operations. In addition, our aggregate DCF and Adjusted EBITDA are presented in notes (4) and (6) to the Preliminary Earnings Contribution by Business Segment tables.
Certain Items are items that are required by GAAP to be reflected in net income, but typically either (i) do not have a cash impact (for example, unrealized and realized foreign exchange gains and losses on the KMI loans and asset impairments), or (ii) by their nature are separately identifiable from our normal business operations and in our view are likely to occur only sporadically (for example, certain gains or losses on asset sales, divestiture costs, legal settlements and casualty losses).
DCF is net income before DD&A adjusted for (i) income tax expense and cash income taxes (paid) refunded; (ii) sustaining capital expenditures; and (iii) Certain Items. DCF is an important performance measure used by us and by external users of our financial statements to evaluate our performance and to measure and estimate our ability to generate cash earnings after servicing our debt and preferred stock dividends, paying cash taxes and expending sustaining capital, that could be used for discretionary purposes such as distributions or expansion capital expenditures. KML uses this performance measure and believes it provides users of its financial statements a useful performance measure reflective of our ability to generate cash earnings to supplement the comparable GAAP measure. DCF should not be used as an alternative to net cash provided by operating activities computed under GAAP. We believe the GAAP measure most directly comparable to DCF is net income. DCF per split-adjusted restricted voting share is DCF divided by average outstanding split-adjusted restricted voting shares, including stock awards that participate in dividends.
Segment EBDA before Certain Items is used by management in its analysis of segment performance and management of our business. The Company believes that Segment EBDA before Certain Items is a useful measure of operating performance because it measures segment operating results before DD&A and certain expenses that are generally not controllable by the operating managers of the respective business segments, such as general and administrative expense, interest expense, income tax expense, and, prior to their pay off in the second quarter of 2017, the foreign exchange losses (or gains) on the KMI loans. General and administrative expenses include such items as employee benefits, insurance, rentals, certain litigation expenses, and shared corporate services including accounting, information technology, human resources and legal services. Segment EBDA before Certain Items is calculated by adjusting Segment EBDA for the Certain Items attributable to a segment, as applicable, which are specifically identified in the footnotes to the accompanying tables.
Adjusted EBITDA is used by the Company and external users of its financial statements, in conjunction with net debt, to evaluate certain leverage metrics. Adjusted EBITDA is EBITDA adjusted for Certain Items, as applicable. We believe the GAAP measure most directly comparable to Adjusted EBITDA is net income. The Company evaluates adjusted EBTIDA in total and does not allocate Adjusted EBITDA amongst equity interest holders as it views Adjusted EBITDA as a measure against our overall leverage.
Adjusted Earnings is net income before Certain Items. Adjusted Earnings is used by certain external users of our financial statements to assess the earnings of our business excluding Certain Items as another reflection of our ability to generate earnings. We believe the GAAP measure most directly comparable to Adjusted Earnings is net income.
Reconciliations of each of the foregoing non-GAAP measure, along with reconciliations of these non-GAAP measures from continuing and discontinued operations, have been provided in the financial tables set out below.
SOURCE Kinder Morgan Canada Limited
View original content: http://www.newswire.ca/en/releases/archive/January2019/16/c1099.html
Keyera Kinder Morgan Trans Mountain pipeline
Follow the BOE Report
Sign up for the BOE Report Daily Digest E-mail
Knowledge Energy Inc. – non-core property divestiture
Documents show Biden plans Day 1 order nixing Keystone XL
Oilpatch woes boost Calgary's downtown office vacancy rates to record levels
Alberta Gas
CAD/GJ
About BOEReport.com
Daily Digest E-mail
Data Partner
BOE Network
© 2021 Grobes Media Inc.


Fully accredited classes that allow you to receive accredited certification. Whether you are seeking certification or recertification call Rendon today .
Courses Temecula and San Diego ACLS, PALS, IV Therapy.
Locations. Select one of our locations to see course schedules and to register for a course. Temecula. 28910 Rancho California Rd. Suite 203, Temecula, CA 92590.
Airway Management Intubation 1 Day Class Private Course On Demand Any Day $299 Need a class on a particular date This 1 day class is 6 hrs and goes from.
About Us. Our instructors are held to a very high standard of excellence. Not only do they have extensive, hands on experience in fields such as nursing, medicine.
Temecula PALS Certification Certified Training At Your.
Courses. We re flexible so that you don t have to be Not only do we offer our regularly scheduled courses, but we can also accommodate any special needs you might have.
Contact Us Temecula and San Diego ACLS, PALS, IV Therapy.
Heartsaver First Aid Skills Evaluation Combo. This course is for people who don t have a medical background, but need to be certified for their job, adoption, or.
Your contact information will only be shared with Dr. Rendon and will not be used for other marketing purposes.


In a bowl, mix all marinade ingredients and let stand 20 minutes in the fridge.
Preheat barbecue on maximum. Oil grill.
Grill chicken for about 6 minutes on each side until cooked. Set aside.
In a small bowl, mix all salsa ingrédients. Set aside.
In a bowl, gently mix all salad ingrédients with grilled chicken and top chicken with corn salsa.