text:
Bid Protest
GEORGIA SAME-SEX MARRIAGE
by hindsonmelton on Jun 27, 2016 • same-sex marriage; Georgia; Obergefell
Georgia's same-sex marriage laws evaporated with the announcement of the 2015 Obergefell v. Hodges decision. The landmark United States Supreme Court decision requires States to: - license a marriage between two people of the same sex, and - recognize a marriage between two people of Read More
Government Control Exception to Late Proposal Rule
by hindsonmelton on Jul 23, 2012 • service-disabled, small business, small disadvantaged business, veteran owned
A government contractor successfully filed a pre-award bid protest challenging the Defense Intelligence Agency (DIA) rejection of its proposal as late. In the case of Electronic On-Ramp, Inc. v. United States, 104 Fed.Cl. 151 (March 28, 2012), the Court of Federal Read More
SDVOSB VOSB Set Asides for FSS Contracts
by hindsonmelton on Jun 16, 2012 • Georgia, SDVOSB, veteran, VOSB
SDVOSB and VOSB have priority for contracts awarded under GSA's FSS (Federal Supply Schedule) procedures. The Department of Veterans Affairs (VA) must conduct market research to determine if there are two or more eligible SDVOSB or VOSB concerns capable of Read More
Bid Protests in the United States Court of Federal Claims
by hindsonmelton on Jun 9, 2012 •
The United States Court of Federal Claims has jurisdiction to hear bid protest cases under the Tucker Act, 28 U.S.C. Section 1491(b). The Tucker Act, as amended by the Administrative Dispute Resolution Act of 1996, Pub.L. No. 104-320 Section 12(a)-(b), waives Read More
Standing to File Bid Protest in Court of Federal Claims
In the case of Digitalis Education Solutions, Inc. v. United States, 664 F.3d 1380 (Jan. 4, 2012). the United States Court of Appeals for the Federal Circuit affirmed the Court of Federal Claims decision that the appellant was not an Read More
by hindsonmelton on May 22, 2012 • GAO
There are several types of bid protests available for interested parties or disappointed bidders in federal agency procurements, including agency protests (Federal Acquisition Regulation 33.103 and Executive Order 12979), protests before the General Accountability Office, and protests filed with the U. S. Court Read More
Court of Federal Claims
by hindsonmelton on May 22, 2012 •
United States Court of Federal Claims - The Tucker Act 28 U.S.C. § 1491 gives the United States Court of Federal Claims jurisdiction to hear claims arising under Section 10(a)(1) of the Contract Disputes Act. This includes claims by or against, or disputes Read More
GAO Sustains Bid Protest – Agency Engaged in Discussions
by hindsonmelton on Feb 16, 2012 • Discussions
In Matter of: Standard Communications, Inc., B-406021 (January 24, 2012), the Comptroller General sustained a bid protest because the agency engaged in discussions with the awardee, but not the protester. The agency characterized it's communications with the awardee as clarifications Read More
Post-Award Bid Protest Sustained for Flawed Award Decision
by hindsonmelton on Dec 29, 2011 • Post-award bid protest
In Firstline Transportation Security, Inc. v. United States, 100 Fed.Cl. 359 (Sept. 27, 2011), the Court sustained a post-award bid protest, finding that the agency's selection of a low-price technically inferior proposal in a best-value procurement was not justified. Non-price Read More
GAO Sustains Protest of Contract Award to Different Legal Entity
by hindsonmelton on Dec 28, 2011 • 8(a), GAO, SBA
In Matter of: W.B. Construction and Sons, Inc., B-405874, B-405874.2, December 16, 2011, GAO sustained a protest that the contracting agency improperly awarded an 8(a) contract to an entity that did not participate in the procurement. The construction contract award Read More


Protocoder code: it will store the graphical interface and the functions that send data to the ZUM board via the Bluetooth of the terminal.
ZUM BT-328 code: it will store the PrintBot Evolution programming, such as the operating modes or the Bluetooth communication.
You can download both codes at the end of this entry. Remember that to run the Protocoder code, you will need to install it on your terminal first (you can download it here).
To modify the Protocoder code, first access the application via your terminal and enter the IP address that appears at the bottom of the browser screen on your computer.
Within the code, we are declaring the button with var btnSiguelinas, and we have to give each button a different name to avoid any conflicts. Then with ui.addButton, we can state that the btnSiguelineas variable will be a button. In brackets and in order, we will write the text that will appear on the button, the position in X and Y, the width and height of the button. Then we will need to indicate the function executed on pressing the button, in this case, sending the word siguelinas (line follower) via Bluetooth.
We are declaring the button with var btn180, but this time it´s different as we are using an image instead of text. Then with ui.addImageButton, we can state that the btn180 variable will be an image button. In brackets and in order, we will write the position in X and Y, the width and height of the button and the name of the image that we want to appear on the button. Then we will need to indicate the function executed on pressing the button, in this case, sending the word 180 via Bluetooth. To add an image or any other file, simply drag it from the file explorer on your computer to the box on the bottom right. Bear in mind that the more simple the name is, the easier the process of entering it into the code will be.
Creating buttons for the Dashboard: To include them, we can do it in the same way as the buttons for the device, only instead of using the ui prefix, we will use the dashboard prefix. By default, the dashboard will not appear, however you can change this by replacing dashboard.show(false); with dashboard.show(true);.
Functions for connecting and disconnecting the Bluetooth: These are the ones included within the btnConectar and btnDesconectar variables. We will also create a variable with the name btClient, which will be used to "interact" via Bluetooth.
Connecting: In order to connect, first we need to create a button with the text "Connect Bluetooth" and within the function activated on pressing the button, we will include Bluetooth connection.
Within this function, as well as connecting the Bluetooth, we will declare the bluetoothOn variable – which serves as the Bluetooth connect/disconnect "signal"´- it is assigned the value 1 and the transparency of the button is changed to 0, which means totally transparent . We will also include some animations such as jump and we will make the device vibrate when connected.
Disconnecting: To disconnect, we need to create a button with the text "Disconnect" and within the function activated on pressing the button, we will include the Bluetooth disconnection.
Within this function, in addition to disconnecting the Bluetooth, we will declare the bluetoothOn variable – which serves as the Bluetooth connect/disconnect "signal"´- it is assigned the value 0 and the transparency of the button is changed to 255, which is opaque .
This function doesn´t have a button, as it will be called up every time that a button is pressed, except for connecting and disconnecting via Bluetooth. To send data via Bluetooth, we will use the btClient.send("="+str+"+"); command. For example, this function sends the car moving forward: =avanzar+. This is how the coding was done in this instance, but you can try another way of coding. The = y + characters are used as delimiters at the beginning and end of the transmission.
We will use some of them to tell Arduino which pins the vitamins are connected to, as well as others such as delays, to change how the program is executed. If the turns are incorrect or if you want to change adjust the angles, you can change the giro_180, giro_90, giro_45 and giro_30 variables.
Within this function, we will start the serial port at a speed of 19200 bauds/s, which is the functioning speed of the ZUM BT-328 board Bluetooth module.
Then we need to indicate where each servo is connected, stop the moving servos and move the servo with the bat ultrasound sensor into central position.
Finally, we will use the pinMode(pin,mode) command to set up the different INPUT and OUTPUT pins as required.
Within this function, we can see the if (Serial.available() >0) command which would translate into "human" language as: If there is data on the serial port, then carry out the following commands. In this case, the commands are to call up the readFromAndroid(); function. This function reads the data sent via the Protocoder application. The other command appearing within loop is writeData();. This function is used to enable different control modes (both manual and external), once the data from the previous function has been read.
Instead of this function, we could use the readString(); function but it would be read more slowly, causing the commands sent from the Protocoder program on our terminal to be delayed in reaching the PrintBot evolution.
writeData();: This function controls the flow of the program, reads the data received from the readFromAndroid() function and carries out one command or another in response to that data.
Mode functions: These are the functions used to switch the PrintBot Evolution onto the automatic modes.
Line follower: This auto mode uses infrared sensors to detect whether the sensor is over a line. The special functions izquierdaLineas and derechaLineas are used in this mode to move just one wheel, instead of two in separate directions, to perform the movement.
Within this function, you can change the maximum distance that will be used to detect obstacles, or in other words, the distance that determines whether an object is considered to be an obstacle or not. To do this, the auxiliary functions Distance and TP_init are used, which enable the bat sensor, send an ultrasound signal, calculate the time taken to read the signal after bouncing back and then, according to that time, calculate the distance. Once we know whether there is an obstacle in front of each of the three positions, we can move the PrintBot towards the clear area.
Light follower: This auto mode is used to move the PrintBot towards the area with the greatest light intensity. To do this, we need to read the value of each pin connected to the LDR modules (light dependent resistor), compare the values, turn to the side with the greatest light intensity and move the PrintBot in a straight line for 1 second.
Change the Protocoder application icons to include images on the buttons rather than text.
Use the infrared sensors to detect the edges. You can see an example of how to do this here.


The National Tuberculosis and Leprosy Control Programme (NTBLCP) has said that tuberculosis (TB) kills not less than 18 Nigerians in every 60 minutes while about 47 people are newly diagnosed every hour.
The situation was made known in a press release by the Agency to commemorate the 2019 World Tuberculosis Day on March 24.
"TB kills 18 Nigerians every hour. Forty-seven Nigerians develop active TB, seven of which are children, every hour," the statement read in part.
March 24 of every year is dedicated by the United Nations to raise public awareness about the devastating health, social and economic consequences of Tuberculosis as well as stepping up efforts to end the global epidemic.
According to the World Health Organisation, tuberculosis is one of the top ten causes of death globally with about 4,500 lives lost per day. It is also identified as the major leading cause of death of the HIV patients. But the WHO said the disease is preventable and curable, while it called for early diagnosis and treatment to prevent spreading the disease to others.
According to the global TB reports in 2017, there are seven countries that accounted for 64 per cent of the burden and thirty countries have been listed to have the high burden of the disease. Nigeria has been included in the list by securing the seventh position.
Other countries which preceded Nigeria is India, Indonesia, China, Philippines, Pakistan, and South Africa. Thus, this makes Nigeria the second country in Africa who have the highest burden of tuberculosis.
The Nigerian Tuberculosis agency has outlined some of the major challenges of tackling tuberculosis in the country to below reporting cases, attributed partly to poor knowledge about the disease, as well as low coverage of the treatment.
Lovette Lawson, the Board Chairman of Stop TB partnership Nigeria, during a pre-World TB day conference in Abuja, said that over 75 per cent of Nigerians with the disease are yet to be diagnosed or receive any form of treatment. This, he had blamed on the lack of awareness among the communities and the stigmatization of those diagnosed with the ailment.
To curb the spread of the disease, Lawson advised Nigerians who have been coughing for more than two weeks to visit health facilities because an infected person can infect 10 to 15 persons, if not quickly treated.
Receiving a vaccine for tuberculosis has been embraced globally as a way of protecting oneself from being infected. Bacilli Calmette-Guerin (BCG) is the vaccine for the prevention of TB and often administered to children at birth.
TB is an airborne disease, that is, it is spread person to person through the air. When persons with the TB coughs, sniff or spit, they propel germs to the air. If a person inhales only a few of these germs, such a person becomes infected. While anybody could be infected, the most at risk are those suffering from other conditions that impair the immune system such as HIV, and the tobacco users.
The Global efforts to combat TB have saved an estimated 54 million lives since the year 2000 and reduced the TB mortality rate by 42%. However, the emergence of drug-resistant TB poses a major health threat and could put at risk the gains made in efforts to end TB. Drug-resistant TB is a public health challenge.
With this year's theme –"It's time", the global leaders, including President Muhammad Buhari, were reminded to urgently act on the commitments made at the United Nations High-level Meeting in September 2018 to end TB.
Also WHO has called on the government of the high burden countries which Nigeria is part of to scale up access with the prevention and treatment of the infectious disease.
It also launched a joint initiative "Find. Treat. All. #EndTB" with the Global Fund and Stop TB Partnership, with the aim of accelerating the TB response and ensuring access to care.


text:
Home / National Teams / U17 Men - Crocs / U17 men down to USA in world champs opener
U17 men down to USA in world champs opener
Posted on Saturday, June 30th, 2012 by Basketball Australia
BOXSCORE Despite 17 points from Dante Exum, the Australian men's Under 17 national team has opened the preliminary round of the FIBA U17 World Championship with an 89-67 loss to tournament favourites the USA on Friday afternoon in Kaunas, Lithuania.…
Despite 17 points from Dante Exum, the Australian men's Under 17 national team has opened the preliminary round of the FIBA U17 World Championship with an 89-67 loss to tournament favourites the USA on Friday afternoon in Kaunas, Lithuania.
Exum, the son of former NBL star Dante Exum, was a stand-out for the Australians and the only player to score in double-figures.
Nicholas Duncan added nine points, 13 rebounds and two blocks for Australia while Mirko Djeric had eight points and six assists.
For the US, Stephen Domingo poured in 17 points to lead five teammates in double-digit scoring as the Americans used a 36-14 third-quarter burst to pull away from Australia.
Despite the loss, the Australians pushed the Americans.
"In the first half they beat us to the basketball too many times," said US coach Don Showalter. "We got outrebounded in the first half. That's probably the first time in my four years here that we've been outrebounded in a half. Obviously in the second half we righted the ship and took care of the little things."
The Americans led wire-to-wire, but came out flat and found that Australia was hard to shake. By the end of the first quarter, which saw Domingo swish in back-to-back threes early in the game, the USA's lead was six points, 18-12.
The second quarter started with both teams swapping buckets, and Australia cut the lead to four, 23-19, at 7:37. The USA hit a 6-3 spurt, however, to expand the gap to 29-22 at 5:56. Australia wouldn't go away and with the help of its zone defense, scored five straight points. Showalter used one of his timeouts to regroup.
When play resumed the Americans strung together a 7-0 run and the expanded their lead to its largest of the half, 36-27, with 1:49 remaining until the break. By halftime, however, Australia was trailing by six points again, 39-33, after outscoring the U.S. 6-3 in the final 1:27.
The second half opened with Australia attempting to chip away, and at 8:11 the score was 43-38. That was as close as the Aussies would get. With the score standing at 46-40, Jahlil Okafor hit three consecutive buckets inside for the US including a huge dunk and the Americans were off and running. Holding Australia to just a free throw during a 5:12 span, the red, white and blue outscored its opponents 19-1 to take a commanding 65-41 lead with 2:25 to go in the stanza.
By the end of the third quarter, the US held a commanding 75-47 lead and despite Australia's efforts in the final period, the Americans cruised to an eventual 89-67 win.
In today's other Group A games, China defeated Egypt 80-68 and Czech Republic edged France 70-64. In Group B Spain (1-0) downed South Korea (1-0) 80-62, while Canada (1-0) went down to the wire against host Lithuania (0-1) and came away with a 68-63 overtime victory.
Australia next face China on Saturday.
Follow the Australian team on the official event website by clicking here.
Australians win 3x3
BA reviews referee pathways

redpajama_set_name: RedPajamaCommonCrawl


text:
Acompsia syriella is a moth of the family Gelechiidae which is endemic to Syria.

Description
The wingspan is about  for males. The forewings are straw yellow, mottled with black scales. The hindwings are grey.

Distribution
Adults have been recorded in mid May.

Etymology
The species is named after the type region.

References

Moths described in 2002
Endemic fauna of Syria
Moths of Asia
Acompsia

redpajama_set_name: RedPajamaWikipedia


text:
Q: FATAL: No bootable medium found! System halted downloaded Windows XP SP3 ISO image from Microsoft.com here http://www.microsoft.com/en-us/download/details.aspx?id=25129 and I am using Oracle's VM VirtualBox to create a new VM. I load it using VM and select the media as the 545 MB .iso I just downloaded and I get "FATAL: No bootable medium found! System halted."
Help?

A: That CD only contains the SP3 update.
It is not a full Windows XP installation CD, and it is not bootable.

redpajama_set_name: RedPajamaStackExchange


Do you ever wish that you could get away from it all?
Go somewhere relaxing for a few days or a week just to focus on you? Wake up each morning in the most beautiful location.
Do Yoga, eat well and be calm.
Then a Yoga Retreats is the place for you.
returning next year dates for 2020 coming soon!
Discover an island blessed with incredible natural beauty, a rich culture and a wealth of wildlife. With its national parks, tea-leaf covered hillsides and ancient architecture, it has multiracial history and a strong Buddhist heritage, the locals are some of the friendliest people on the planet, always willing to go that extra mile. Sri Lanka is a beauty to behold, perfect to relax and unwind making it a wonderful destination for a Yoga Retreat.
Based at the fabulous 4-star Grand Hotel in Porto Cervo, you will be surrounded by the stunning natural beauty of Costa Smeralda.
Based at the fabulous 4-star Hotel Mlini Newly built in 2015 in the village of Mlini, right by the beach, just 15 minutes from the old town of Dubrovnik.
On an all-inclusive Yoga Holiday in Southern Italy with amazing walking and hiking trails.
Set in a beautiful architecturally designed country house located in the middle of vineyards and olive groves.
With amazing views of the Majella mountains and Adriatic Sea.
Based at the fabulous 4-star Hotel Cala d'Or, you will be amongst the stunning natural beauty of eastern Majorca. You'll be situated just 5 minutes' walk from the town centre, and an abundance of restaurants and cafes.
Zoe and Claire invites you to there Summer Yoga & Essential Oils Day Retreat at The Treehouse. The Treehouse is set in idyllic private woods in Beaulieu, truly one of Beaulieu's greatest hidden gems!
I attended Zoe's Goa retreat in 2016 and had a truly amazing time. The yoga schedule and teachers were fantastic and irrespective of yoga ability or fitness level, there was something for everyone in the classes.


text:
Miriam Gerald Odemba ou Miriam Odemba, née le  à Arusha, en Tanzanie, est une top modèle Tanzanienne. Elle est l'un des mannequins les plus connus de son pays, et a commencé ce parcours dans le mannequinat et les concours de beauté à un âge précoce.

Éléments biographiques
Son enfance a été difficile. Mais elle bénéficie des feux de la rampe dès 1997, encore adolescente, lorsqu'elle  remporte le prix Miss Temeke. L'année suivante, elle prend part à plusieurs concours dont le concours Miss Afrique de l'Est (Miss East Africa beauty), et y termine deuxième. Elle a est sélectionné à Nice au Elite Model Look 1999, concours organisé chaque année par l'agence de mannequins Elite Model Management.  Sous contrat avec l'Agence Elite, elle travaille un an à New York, un an en Afrique du Sud, puis cinq ans en Chine, en contrat avec Cherry Modelling Agency.

Elle revient en 2008 en Tanzanie et aux concours de beauté, devient Miss Tanzanie et participe au concours de Miss Earth 2008, où elle est  dauphine. Elle tente un moment de créer une activité dans le domaine de la mode en Tanzanie, tout en se préoccupant de la protection de l'environnement, puis travaille en Europe, à Paris en particulier, en tant que freelance Top model.

Références

Liens externes

Mannequin femme tanzanien
Naissance en février 1983
Naissance à Arusha


Polling in 95 Parliamentary constituencies, spread over 11 States and one Union Territory was held on Thursday under the second phase of the general election.
Voting was held for 38 seats in Tamil Nadu, 14 in Karnataka, 10 in Maharashtra, eight in Uttar Pradesh, five each in Assam, Bihar and Odisha, 3 each in Chhattisgarh and West Bengal, two in Jammu and Kashmir and one each in Manipur and Puducherry.
Voting also took place for 35 Assembly seats in Odisha and 18 in Tamil Nadu.
In West Bengal, around 72 per cent polling has been reported till 5 PM for three parliamentary constituencies of Jalpaiguri, Raigunj and Darjeeling.
In Bihar, over 56 per cent polling has been recorded for five Lok Sabha constituencies till 5 pm.
Maximum 60 per cent voting was recorded in Kishanganj parliamentary constituency.
In Tamil Nadu, around 52 per cent polling has been recorded till 3 PM for 38 Lok Sabha seats.
Karur recorded the highest voter turnout at around 57 per cent, while Chennai Central clocked the lowest with nearly 45 per cent.
In Jammu and Kashmir, over 38 per cent votes were polled for two Parliamentary Constituencies of Udhampur and Srinagar till 3 pm.
In Udhampur constituency, which is spread over 6 districts, around 64 per cent polling was recorded in Kathua.
In Srinagar constituency, around 17 per cent polling was recorded in Badgam district.


Very thorough, knowledgeable, and caring. He focused on conservative care for my problem first, with surgery as a last resort. Highly recommend!
Dr. Ha spent about 2 minutes with me each time I saw him and said nothing that helped me on my quest to figure out why I've been having chronic back pain. Said my MRI was fine and sent me on my way. Very poor personal skills and is definitely in his field for the money. Doesn't care about his patients. Would never rev comment him.
Dr Ha performed cervical fusion on my spine. The operation was successful. He is friendly, knowledgeabe, and timely.I would not hesitate to recommend him to anyone with a spinal problem.
Dr. Ha is uncaring and rude. X-rays and an MRI revealed multiple bulging discs and arthritis. Dr. Ha said "this is something you'll have to deal with the rest of your life. And it's just going to get worse". He had no suggestions for pain relief or PT or anything to help. I left his office and immediately scheduled an appointment with a wonderful doctor at The Center. With steroids and muscle relaxers I was much better within a few days.
Dr. Chae G Ha is similar to the following 4 Doctors near Bend, OR.
Have you had a recent visit with Dr. Chae G Ha? Select a star to let us know how it was.


text:
[Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01 02 03 04 05 06 07
Internet Engineering Task Force                                R. Shakir
Internet-Draft                                                       C&W
Intended status: Informational                          October 20, 2011
Operational Requirements for Enhanced Error Handling Behaviour in BGP-4
draft-ietf-grow-ops-reqs-for-bgp-error-handling-02
BGP-4 is utilised as a key intra- and inter-Autonomous System routing
protocol in modern IP networks.  The failure modes as defined by the
original protocol standards are based on a number of assumptions
around the impact of session failure.  Numerous incidents both in the
global Internet routing table and within Service Provider networks
have been caused by strict handling of a single invalid UPDATE
message causing large-scale failures in one or more Autonomous
Systems.
This memo describes the current use of BGP-4 within Service Provider
networks, and outlines a set of requirements for further work to
enhance the mechanisms available to a BGP-4 implementation when
erroneous data is detected.  Whilst this document does not provide
specification of any standard, it is intended as an overview of a set
of enhancements to BGP-4 to improve the protocol's robustness to suit
its current deployment.
Drafts is at http://datatracker.ietf.org/drafts/current/.
This Internet-Draft will expire on April 22, 2012.
Shakir                   Expires April 22, 2012                 [Page 1]
Internet-Draft     Requirements for BGP Error Handling      October 2011
1.1.  Role of BGP-4 in Service Provider Networks . . . . . . . .  3
1.2.  Overview of Operator Requirements for BGP-4 Error
Handling . . . . . . . . . . . . . . . . . . . . . . . . .  4
2.  Errors within BGP-4 UPDATE Messages  . . . . . . . . . . . . .  6
2.1.  Classifying BGP Errors and Expected Error Handling . . . .  7
2.1.1.  Critical BGP Errors  . . . . . . . . . . . . . . . . .  7
2.1.2.  Semantic BGP Errors  . . . . . . . . . . . . . . . . .  8
3.  Avoiding use of NOTIFICATION . . . . . . . . . . . . . . . . .  9
4.  Recovering RIB Consistency . . . . . . . . . . . . . . . . . . 11
5.  Reducing the Impact of Session Reset . . . . . . . . . . . . . 13
6.  Operational Toolset for Monitoring BGP . . . . . . . . . . . . 15
7.  Operational Complexities Introduced by Altering RFC4271  . . . 19
7.1.  Reducing the Network Impact of Session Teardown  . . . . . 21
8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 22
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24
11.2. Informational References . . . . . . . . . . . . . . . . . 25
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 27
Where BGP-4 [RFC4271] is deployed in the Internet and Service
Provider networks, numerous incidents have been recorded due to the
manner in which [RFC4271] specifies errors in routing information
should be handled.  Whilst the behaviour defined in the existing
standards retains utility, the deployments of the protocol have
changed within modern networks, resulting in significantly different
demands for protocol robustness.  Whilst a number of Internet Drafts
have been written to begin to enhance the behaviour of BGP-4 in terms
of the handling of erroneous messages, this memo intends to define a
set of requirements for ongoing work.  These requirements are
considered from the perspective of a Network Operator, and hence this
draft does not intend to define the protocol mechanisms by which such
error handling behaviour is to be implemented.
1.1.  Role of BGP-4 in Service Provider Networks
BGP was designed as an inter-Autonomous System (AS) routing protocol
and hence many of the error handling mechanisms within the protocol
specification are designed to be conducive to this role.  In general,
this consideration as an inter-AS routing propagation mechanism
results in the view that a BGP session propagates a relatively small
amount of network-layer reachability information (NLRI) between two
ASes.  In this case, it is the expectation of session resilience for
those adjacencies that are key to routing continuity (for example, it
is expected that two networks peering via BGP would connect multiple
times in order to safeguard equipment or protocol failure).  In
addition, there is some expectation of multiple paths to a particular
NLRI being available - it would be expected that a network can fall
back to utilising alternate, less direct, paths where a failure of a
more direct path occurs.
Traditional network architectures would deploy an Interior Gateway
Protocol (IGP) to carry infrastructure and customer prefixes, with an
Exterior Gateway Protocol (EGP) such as BGP being utilised to
propagate these prefixes to other Autonomous Systems.  However, with
the growth of IP-based services, this is no longer considered best
practice.  In order to ensure that convergence is within acceptable
time bounds, the amount of routing information carried within the IGP
is significantly reduced - and tends to be only infrastructure
prefixes. iBGP is then utilised to propagate both customer, and
external prefixes within an AS.  As such, BGP has become an IGP, with
traditional IGPs acting as a means by which to propagate the routing
information which is required to establish a BGP session, and reach
the egress node within the local routing domain.  This change in role
presents different requirements for the robustness of BGP as a
routing protocol - with the expectation of similar level of
robustness to that of an IGP being set.
Along with this change in role, the nature of the IP routing
information that is carried has changed.  BGP has become a ubiquitous
means by which service information can be propagated between devices.
For instance, BGP is utilised to carry routing information for IP/
MPLS VPN services as described in [RFC4364].  Since there is an
existing deployment of the protocol between PE devices in numerous
networks, it has been adapted to propagate this routing information,
as its use limits number of routing protocols required on each
device.  This additional information being propagated represents a
large change in requirement for the error handling of the protocol -
where session failure occurs, it is likely a complete service outage
for at least a subset of a network's customers is experienced where
an erroneous packet may have occurred within a different sub-topology
or even service (a different address family for example).  For this
reason, there is a significant demand to avoid service affecting
failures that may be triggered by routing information within a single
sub-topology or service.
Both within Internet and multi-service routing architectures, a
number of BGP sessions propagate a large proportion of the required
routing information for network operation.  For Internet routing,
these are typically BGP sessions which propagate the global routing
table to an AS - failure of these sessions may have a large impact on
network service, based on a single erroneous update.  In an multi-
service environment, typical deployments utilise a small number of
core-facing BGP sessions, typically towards route reflector devices.
Failure of these sessions may also result in a large impact to
network operation.  Clearly, the avoidance of conditions requiring
these sessions to fail is of great utility to any network operator,
and provides further motivation for the revision of the existing
Whilst the behaviour in [RFC4271] is suited to ensuring that BGP
messages with erroneous routing information in are limited in scope
(by means of session reset), with the above considerations, it is
clear that this mechanism is not suited to all deployments.  It
should, however, be noted that the change in scope affects the
handling only of errors occurring after BGP session establishment.
There is no current operational requirement to amend the means by
which error handling in session establishment, or liveliness
detection, are performed.
1.2.  Overview of Operator Requirements for BGP-4 Error Handling
It is the intention of this document to define a set of criteria for
the manner in which a revised error handling mechanism in BGP-4 is
required to conform.  The motivation for the definition of these
requirements can be summarised based on certain behaviour currently
present in the protocol that is not deemed acceptable within current
operational deployments, or where there is a short-fall in the tool
set available to an operator.  These key requirements can be
summarised as follows:
o  It is unacceptable within modern deployments of the BGP-4 protocol
that a single erroneous UPDATE packet affects prefixes that it
does not carry.  This requirement therefore requires some
modification to the means by which erroneous UPDATE packets are
handled, and reacted to - with a particular focus on avoiding the
use of the NOTIFICATION message.
o  It is recognised that some error conditions may occur within the
BGP-4 protocol may not always be handled gracefully, and may
result in conditions whereby an implementation cannot recover.  In
these (and similar) cases, it is unacceptable for an operator that
this reset of the BGP-4 session results in interruption to
forwarding packets (by means of withdrawing prefixes installed by
BGP-4 into a device's RIB, and subsequently FIB).  To this end,
there is a requirement to define a session reset mechanism which
provides session re-initialisation in a non-destructive manner.
o  Further to the requirements to provide a more robust protocol, the
current visibility into error conditions within the BGP-4 protocol
is extremely limited - where further modifications to this
behaviour are to be made, complexity is likely to be added.  Thus,
to ensure that BGP-4 is manageable, there are requirements for
mechanisms by which the protocol can be examined and monitored.
This document describes each of these requirements in further depth,
along with an overview of means by which they are expected to be
achieved.  In addition, the mechanism by which the enhancements
meeting these requirements are to interact is discussed.
2.  Errors within BGP-4 UPDATE Messages
Both through analysis of incidents occurring with the Internet DFZ,
and multi-service environments utilising BGP-4 to signal service or
routing information, a number of different classes of errors within
BGP-4 UPDATE messages have been observed.  In order to consider the
applicability of enhanced error handling mechanisms, it is possible
to divide these errors into a number of sub-classes, particularly
focusing around the location of the error within the UPDATE message.
Where an UPDATE message is considered invalid by a BGP speaker due to
an error within a path attribute that is not the NLRI (where the
definition of NLRI includes reachability information encoded in the
MP_REACH_NLRI and MP_UNREACH_NLRI attributes as specified in
[RFC4760]) it is a requirement of any enhanced error handling
mechanism to handle the error in a manner focused on the NLRI
contained within the message.  Since in this case, the message
received from the remote peer is syntactically valid, it is
considered that such an UPDATE is indicative of erroneous data within
a path attribute.  The impact of the current behaviour defined within
the protocol makes the implication that the BGP speaker from whom the
message is received is now an invalid path for all NLRI announced via
the session - which results in a disproportionate impact to overall
network operation.  In particular scenarios (such as networks with
centralised BGP route reflection) such action can result in a loss of
all reachability to a network.  In other contexts (such as the
Internet DFZ), it cannot be assumed that the BGP speaker from whom
the UPDATE message is received is directly responsible for the
erroneous information contained within the message.
Two further error cases exist within UPDATE messages, both of which
are related to the mechanisms that are applicable to messages
received where some difficulty exists in parsing the entire BGP
message.  The two cases concern those cases where a valid NLRI
attribute can be extracted, and those where such an attribute is not
able to be parsed.  In these cases, errors in the packing of
attributes within a BGP message may have occurred.  Such errors are
likely indicative of an error specifically caused by the remote BGP
speaker.  It is, however, desirable to an operator that such errors
are handled without affecting all NLRI across a BGP session.  As
such, there is a key requirement to maximise the number of cases in
which it is possible to extract NLRI from a BGP UPDATE message.  To
this end, it is required that where possible the MP_REACH and
MP_UNREACH attributes are utilised for encoding all NLRI (including
IPv4 Unicast), and that this attribute is included as the first
attribute of a BGP UPDATE message (as originally recommended in
[I-D.chen-ebgp-error-handling]).  Such a change to the order of
inclusion of this attribute maximises the number of cases in which
NLRI can be extracted from an UPDATE.  Where this is possible, it is
again required that the error handling mechanisms utilised should be
directly applied to the NLRI included in the UPDATE.
For all cases whereby NLRI can be obtained from an UPDATE message, it
is expected that the requirements outlined in Section 3 should be
considered by any enhancement to the BGP-4 protocol.
In the case that it is not possible to completely parse the NLRI
attribute from the UPDATE message received from a peer, it is
extremely likely that this is indicative of a serious error with
either the process of attribute packing, or buffer usage on the
remote BGP speaker.  In this case, clearly, it is not possible to
apply any error handling mechanism that is limited to a specific set
of NLRI, since an implementation has no knowledge of the NLRI
included within the UPDATE message.  In addition, such errors are
considered to be relatively fundamental to the operation of a BGP
implementation, and hence may indicate a case whereby significant
system errors have occurred.  The current BGP-4 standard results in a
BGP speaker restarting a session with the remote BGP speaker.
However where such an error does occur, it is required that a
graceful mechanism is utilised to provide a lower impact to network
operation.  The requirements for enhancements of this nature to BGP-4
are outlined in Section 5, with the requirements outlined therein
focused on providing a means by which system integrity can be
restored whilst allowing for continued network operation.
2.1.  Classifying BGP Errors and Expected Error Handling
It is clearly of advantage for BGP-4 implementations to utilise a
consistent set of error handling mechanisms for the different types
of errors that are described in Section 2, and provide consistent
nomenclature to refer to them.  It is therefore suggested that errors
that are indicative of larger scale failures of a BGP speaker, and
hence require some error handling at the session level are referred
to as 'critical' errors, whilst those errors that are identified
based on incorrect content of one of more attributes of a message are
referred to as 'semantic' errors.
2.1.1.  Critical BGP Errors
As described in this document, it is of advantage to limit the number
of 'critical' errors that occur within the protocol, therefore, based
on analysis of the processing of BGP UPDATE messages, it is required
that 'critical' error handling behaviour is applied to:
o  UPDATE Message Length errors - whereby the specified overall
UPDATE message length is inconsistent with sum of the Total Path
Attribute and Withdrawn Routes length.  In this case, this is
indicative of message packing failure, whereby the NLRI may not be
correctly extracted.
o  Errors Parsing the NLRI attributes of an UPDATE message - where
NLRI is carried in either the IPv4-Unicast Advertised or Withdrawn
routes, or in the MP_REACH_NLRI or MP_UNREACH_NLRI attributes
[RFC2858], it is not possible to target error handling mechanisms
to specific NLRI, and hence session level mechanisms must be
utilised.
It is expected that those requirements outlined in Section 5 are
utilised to provide session-level handling of those errors identified
as 'critical'.
2.1.2.  Semantic BGP Errors
Where a BGP message is correctly formed, a number of cases exist
whereby the contents of the UPDATE are not valid - in these cases,
this represents errors that can be identified to affect specific
NLRI.  The following cases are expected to be classified a semantic
o  Zero or invalid length errors in path attributes excluding those
containing NLRI, or where the length of all path attributes
contained within the UPDATE does not correspond to the total path
attributes length.  In this case, the NLRI can be correctly
extracted, and hence acted upon.
o  Messages where invalid data or flags are contained in a path
attribute that does not relate to the NLRI.
o  UPDATE messages missing mandatory attributes, unrecognised non-
optional attributes or those that contain duplicate or invalid
attributes (be they unsupported or unexpected).
o  Those messages where the NEXT_HOP, or MP_REACH next-hop values are
missing, length zero, or invalid for the relevant AFI/SAFI.
In these cases, it is expected that these errors can be handled
gracefully, following the requirements detailed in Section 3 and
Section 4 of this memo.
3.  Avoiding use of NOTIFICATION
The error handling behaviour defined in RFC4271 is problematic due to
the limited options that are available to an implementation.  When an
erroneous BGP message is received, at the current time, the
implementation must either ignore the error, or send a NOTIFICATION
message, after which it is mandatory to terminate the BGP session.
It is apparent that this requirement is at odds with that of protocol
robustness.
There is significant complexity to this requirement.  The mechanism
defined in [I-D.chen-ebgp-error-handling] describes a means by which
no NOTIFICATION message is generated for all cases whereby NLRI can
be extracted from an UPDATE.  The NLRI contained within the erroneous
UPDATE message is considered as though the remote BGP speaker has
provided an UPDATE marking it as withdrawn.  This results in a limit
in the propagation of the invalid routing information, whilst also
ensuring that no traffic is forwarded via a previously-known path
that may no longer be valid.  This mechanism is referred to as
"treat-as-withdraw".
Whilst this behaviour results in avoiding a NOTIFICATION message,
keeping other routing information advertised by the remote BGP
speaker within the RIB, it may result in unreachability for a sub-set
of the NLRI advertised by the remote speaker.  Two cases should be
considered - that where the entry for a prefix in the Adj-RIB-In of
the neighbour propagating an erroneous packet is utilised, and that
where the prefix installed in the device's RIB is learnt from another
BGP speaker.  In the former case, should the identified NLRI not be
treated as withdrawn, the original NLRI is utilised within the global
RIB.  However, this information is potentially now invalid (i.e. it
no longer provides a valid forwarding path), whilst an alternate
(valid) path may exist in another Adj-RIB-In.  By continuing to
utilise the NLRI for which the UPDATE was considered invalid, traffic
may be forwarded via an invalid path, resulting in routing loops, or
black-holing.  In the second case, no impact to the forwarding of
traffic, or global RIB, is incurred, yet where treat-as-withdraw is
implemented, possibly stale routing information is purged from the
Adj-RIB-In of the neighbour propagating errors.
Whilst mechanisms such as "treat-as-withdraw" are currently
documented, the proposals are limited in their scope - particularly
in terms of restrictions to implementation only on eBGP sessions.
This limitation is made based on the view that the BGP RIB must be
consistent across an autonomous system.  By implementing treat-as-
withdraw for a iBGP session, one or more routers within the
Autonomous System may not have reachability to a prefix, and hence
blackholing of traffic, or routing loops, may occur.  It should,
however, be considered if this view is valid, in light of the manner
in which BGP is utilised within operator networks.  Inconsistency in
a RIB based on a single UPDATE being treated as withdrawn may cause a
inconsistency in a single sub-topology (e.g.  Layer 3 VPN service),
or a service not operating completely (in the case of an UPDATE
carrying service membership information).  Where a NOTIFICATION and
teardown is utilised this is destructive to all sub-topologies in all
address family identifiers (AFIs) carried by the session in question.
Even where mechanisms such as multi-session BGP are utilised, a whole
AFI is affected by such a NOTIFICATION message.  In terms of routing
operation, it is therefore far less costly to endure a situation
where a limited sub-set of routing information within an AS is
invalid, than to consider all routing information as invalid based on
a single trigger.
It is considered that, if extended to cover iBGP, the mechanisms
described in [I-D.chen-ebgp-error-handling] and
[I-D.ietf-idr-optional-transitive] provide a means to avoid the
transmission of a NOTIFICATION to a remote BGP speaker based on a
single erroneous message, where at all possible, and hence meet this
requirement.  The failure cases whereby NLRI cannot be extracted from
the UPDATE message represent a case whereby the receiving system
cannot handle the error gracefully based on this mechanism.
Shakir                   Expires April 22, 2012                [Page 10]
4.  Recovering RIB Consistency
The recommendations described in Section 3 may result in the RIB for
a topology within an AS being inconsistent across the AS' internal
routers.  Alternatively, where such mechanisms are deployed at an AS
boundary, interconnects between two ASes may be inconsistent with
each other.  There are therefore risks of traffic blackholing, due to
missing routing information, or forwarding loops.  Whilst this is
deemed an acceptable compromise in the short term, clearly, it is
suboptimal.  Therefore, a requirement exists to provide mechanisms by
which a BGP speaker is able to recover the consistency of the Adj-
RIB-In for a particular neighbour.
In the general case, the consistency of the BGP RIB can be recovered
by re-requesting the entire Adj-RIB-Out of a remote BGP speaker is
re-advertised.  A mechanism to achieve this re-advertisement is
defined within the ROUTE-REFRESH specification [RFC2918].  It is
envisaged that by requesting a refresh of all NLRI advertised by a
BGP speaker, any NLRI which has been withdrawn due to being contained
within an invalid UPDATE message is re-learnt.  Where a ROUTE REFRESH
is used to directly perform a consistency check between the Adj-RIB-
Out of a remote device, and the Adj-RIB-In of the local BGP speaker,
a demarcation between the ROUTE-REFRESH, and normal UPDATE messages
is required (in order that an "end" of the refresh can be used to
identify any 'stale' NLRI) - [I-D.keyur-bgp-enhanced-route-refresh]
provides a means by which the ROUTE-REFRESH mechanism can be extended
to meet this requirement.
Whilst re-advertisement of the whole BGP RIB provides a means by
which withdrawn NLRI can be re-advertised, there are some scaling
implications that must be considered.  In the case that a ROUTE-
REFRESH is generated, all NLRI must be re-packed into UPDATE messages
and advertised by one speaker on the BGP session, whilst the other
must receive all UPDATE messages, and validate the RIB's consistency.
Clearly, it is advantageous to avoid this work where possible.
It is envisaged that during routing inconsistencies caused by
utilising the 'treat-as-withdraw' mechanism, the local BGP speaker is
aware that some routing information was not able to be processed -
due to the fact that an UPDATE message was not parsed correctly.
Since this mechanism (as discussed in Section 3) requires the local
BGP speaker to have determined the set of NLRI for which an erroneous
UPDATE message was received, it is possible to use a targeted
mechanisms to re-request the specific NLRI that was contained within
the erroneous UPDATE message.  By re-requesting, this provides the
remote BGP speaker an opportunity to re-transmit the NLRI - possibly
providing an opportunity to leverage alternative methods to build the
UPDATE message.  Such a request requires extension to the existing
BGP-4 protocol, in terms of specific UPDATE generation filters with a
transient lifetime.  It is envisaged that the work within
[I-D.zeng-one-time-prefix-orf] provides a mechanism allowing targeted
elements of the Adj-RIB-In for a BGP neighbour to be recovered.
It is of particular note for both means of recovering RIB consistency
described that these are effective only when considering transitive
errors within an implementation - for instance, should an RFC
interpretation error within an implementation be present, regardless
of the number of times a specific UPDATE is generated, it is likely
that this error condition will persist (as it may with the existing
behaviour defined by [RFC4271]).  For this reason, there is an
requirement to consider the means by which such consistency recovery
mechanisms are utilised.  It is not advisable that a transitive
filter and advertisement mechanism is triggered by all error handling
events due to the load this is likely to place on the neighbour
receiving such a request.  Where this BGP speaker is a relatively
centralised device - a route reflector (as described by [RFC4456])
for example - the act of generation of UPDATE messages with such
frequency is likely to cause disproportionate load.  It is therefore
an operational requirement of such mechanisms that means of request
dampening be required by any such extension.
5.  Reducing the Impact of Session Reset
Even where protocol enhancements allow errors in the BGP-4 protocol
to cease to trigger NOTIFICATION messages, and hence reset a BGP
session, it is clear that some error conditions may not be exited.
In particular, errors due to existing state, or memory structures,
associated with a specific BGP session will not be handled.  It is
therefore important to consider how these error conditions are
currently handled by the protocol.  It should be noted that the
following discussion and analysis considers only those NOTIFICATION
messages generated in response to errors in UPDATE messages (as
defined by Section 6.3 in [RFC4271]).
The existing NOTIFICATION behaviour triggers a reset of all elements
of the BGP-4 session, as described in Section 6 of [RFC4271].  It is
expected that session teardown requires an implementation to re-
initialise all structures and state required for session maintenance.
Clearly, there is some utility to this requirement, as error
conditions in BGP are, in general, exited from.  However, this
definition is responsible for the forwarding outages within networks
utilising BGP for route propagation when each error is experienced.
The requirement described in Section 3 is intended to reduce the
cases whereby a NOTIFICATION is required, however, any mechanism
implemented as a response to this requirement by definition cannot
provide a session reset to the extent of that achieved by the current
In order to address this, there is a requirement for a means by which
a BGP speaker can signal that an unhandled error condition in an
UPDATE message occurred - requiring a session reset - yet also
continue to utilise the paths advertised by the neighbour that are
currently in use within the RIB.  In this case, the Adj-RIB-In
received from the neighbour is not considered invalid, despite a
NOTIFICATION, and session reset, being required.  This set of
requirements is akin to those answered by the BGP Graceful Restart
mechanism described in [RFC4724].  Since the operational requirement
in this case is to provide a means to achieve a complete session
restart without disrupting the forwarding path of those prefixes in
use within a BGP speaker's RIB, it is expected that utilising a
procedure similar to the Graceful Restart mechanism meets the error
handling requirement.  By responding to an error condition (repeated
or otherwise) with a message indicating that an error that cannot be
handled has occurred, forcing session reset, whilst retaining
forwarding information within the RIB allows forwarding to all
prefixes within a system's RIB to continue, whilst the session
restarts.  It is envisaged that the additional complexity introduced
by the introduction of such a mechanism can be limited by extending
existing BGP messages - one such approach is proposed in
[I-D.keyupate-idr-bgp-gr-notification].  By placing a time bound on
the restart lifetime, should an error condition not be transient -
for example, should an error have occurred with the BGP process,
rather than a specific of the BGP session - the remote BGP speaker is
still detected as an invalid device for forwarding.
It should, however, be noted that a protocol enhancement meeting this
requirement is not able to solve all error conditions - however, a
complete restart of the BGP and TCP session between two BGP speakers
implements an identical recovery mechanism to that which is achieved
by the existing behaviour.  Where an error condition such as memory
or configuration corruption has occurred in a BGP implementation, it
is expected that a mechanism meeting this requirement continues to
detect this, by means of a bound on time for session restart to
occur.  Whilst there may be some consideration that packets continue
to be forwarded through a device which can be in an failure mode of
this nature for a longer period, due to this requirement, the
architecture of modern IP routers should be considered.  A divided
forwarding and control plane is common in many devices, as well as
process separation for software-based devices - corruption of a
specific protocol daemon does not necessarily imply forwarding is
affected.  Indeed, where forwarding behaviour of a device is
affected, it is envisaged that a failure detection mechanism (be it
Bidirectional Forwarding Detection, or indeed BGP KEEPALIVE packets)
will detect such a failure in almost all cases, with the symptomatic
behaviour of such a failure being an invalid UPDATE message in very
few other cases.
6.  Operational Toolset for Monitoring BGP
A significant complexity that is introduced through the requirements
defined in this document is that of monitoring BGP session status for
an operator.  Although the existing error handling behaviour causes a
disproportionate failure, session failure is extremely visible to
most operational personnel within a Network Operator due to both
existing definitions of SNMP trap mechanisms for BGP, along with the
forwarding impact typically caused by such a failure.  By introducing
mechanisms by which errors of this nature are not as visible, this is
no longer the case.  There is a requirement that where subsets of the
RIB on a device are no longer reachable from a BGP speaker, or indeed
an AS, that some visibility of this situation, alongside a mechanism
to determine the cause is available to an operator.  Whilst, to some
extent, this can be solved by mandating a sub-requirement of each of
the aforementioned requirements that a BGP speaker must log where
such errors occur, and are hence handled, this does not solve all
cases.  In order to clarify this requirement, the example of the
transmission of an erroneous Optional Transitive attribute can be
considered.  Since, by definition, there is no requirement for all
BGP speakers to parse such an attribute, a receiving router may treat
NLRI as withdrawn based on an erroneous attribute not examined by its
neighbour.  In this case, the upstream device or network, propagating
the UPDATE, has no visibility of this error.  Operationally, however,
it is of interest to the upstream router operator that such invalid
information was propagated.
The requirement for logging of error conditions in transmitted BGP
messages, which are visible to only the receiver, cannot be achieved
by any existing BGP message, or capability.  It is envisaged that
each erroneous event should be transmitted to the remote peer -
including the information as to the set of NLRI that were considered
invalid.  Whilst with some mechanisms this is achieved by default
(for example, One-Time Prefix ORF [I-D.zeng-one-time-prefix-orf]
(Outbound Route Filtering) will transmit the set of prefixes that are
required), the operator requirement is to know which prefixes may
have been unreachable in all cases.  It is envisaged that an
extension to meet this requirement will allow for such information to
be transmitted between peers, and hence logged.  Such a mechanism may
provide further utility as a either a diagnostic, or logging toolset.
As such, it is possible to divide the messages that are required in
order to provide further visibility into BGP for an operator.  Such a
division can be made both due to the required means of message
transmission, alongside the criticality of each request.
o  Messages required to replace NOTIFICATION - In cases where the
error handling mechanisms defined by [RFC4271] currently result in
a NOTIFICATION message being generated, a number of the
requirements detailed within this document result this message
being suppressed.  Despite this change, the error condition's
occurrence is still of interest to an operator, since some form of
invalid data has been received on a session in order to provide
both monitoring and troubleshooting capabilities.  It therefore
considered that an implementation must generate a message both
locally, and transmitted to the remote peer, based on the such a
condition.  Where such a message is transmitted to the remote
peer, it is considered that the BGP session via which the
erroneous UPDATE message was received as transport to the remote
peer.  The information transmitted in such a message should be
minimised to allow identification of the paths which were
considered erroneous (i.e. restricting the information to that
which is directly relevant to a network operator in the case of an
error condition occurring).  Any delay to convergence on the
session in question is considered to be acceptable, given the
suboptimal nature of the reception of invalid routing information
via a BGP session.  Further concerns regarding such a mechanism
relate to the load generated on the BGP speaker in question,
however, it must be considered that in the case of an erroneous
UPDATE being received, and the 'treat-as-withdraw' mechanism being
utilised, where the erroneous path is removed from the Loc-RIB,
there is likely to be a requirement to generate UPDATE messages
withdrawing the prefix from all further BGP speakers to which the
prefix is advertised.  The load generated by the generation of
such UPDATEs is likely to be much greater than that of
transmitting error information via a logging message type back to
the speaker from which it was received.  It is envisaged that
light-weight BGP message-based signalling mechanisms such as the
ADVISORY message types detailed in
[I-D.frs-bgp-operational-message] provide a suitable means to
satisfy this requirement.
o  Additional Diagnostic Capabilities for BGP - In a number of cases,
there is an operational requirement to further debug erroneous BGP
UPDATE messages, along with the particulars of the state of a BGP
speaker.  For instance, where an invalid BGP UPDATE message is
transmitted between two BGP speakers, the exact format of the
UPDATE message is of interest to an operator, as this information
provides a clear indication of an message considered to be
erroneous by the BGP speaker to which it was transmitted.  In this
case, it is considered of great utility that the entire UPDATE
message is transmitted back to the advertising speaker, in order
to allow for further debugging to occur.  Whilst such information
is particularly useful to an operator, it clearly provides
information that is not key to protocol operation - for this
reason, it is expected that some of the concerns regarding the
additional complexity, and load that a BGP speaker is subjected to
is not acceptable.  For this reason, it is required that where
mechanisms are developed to support this requirement, messages of
this nature can be supported both within an existing BGP session,
and via a dedicated separate session, be it BGP carrying messages
such as those defined in [I-D.frs-bgp-operational-message] or a
dedicated monitoring protocol akin to BMP described in
[I-D.ietf-grow-bmp].
Whilst the operational requirement for such monitoring tools to allow
for visibility into BGP is clearly agreed upon, the means by which
such messages are transmitted between two BGP speakers is likely to
be dependent upon both the positions of the speakers in question (for
instances, the requirements for such a protocol may differ where a
session is between two ASBRs under separate administration).  The
introduction of additional message types to the BGP protocol clearly
introduces further complexity - and leaves room for further
implementation and standardisation errors that may compromise the
robustness of the BGP protocol.  In addition, the queuing and
scheduling of these BGP messages must be interleaved with the
transmission of the key protocol messages - such as KEEPALIVE and
UPDATE packets.  It is therefore a concern that should a large number
of messages specifically for operational visibility be transmitted,
this will delay the transmission of UPDATE packets, and hence
adversely affect the end-to-end convergence time for NLRI carried
within BGP.  The operational requirement for why messages are
advantageous to be in-band to a protocol should also be considered.
In particular, it should be noted that where such information is to
be transmitted between administrative boundaries a BGP session
represents an existing channel exists between the two ASes.  This
channel is considered to be secure insofar as the routing
information, and requests sent via the session are considered to come
from a trusted source.  Since error information relates to both a
particular attachment, and is key to ensuring that such a session is
operating as expected, it is considered of great operational benefit
that this information is transmitted over this channel.  In addition,
the overall system scalability is improved by such in-band
transmission.  It is expected that erroneous information resulting in
the 'treat-as-withdraw' mechanism being utilised is relatively
infrequently transmitted between two peers (when compared to the
frequency of UPDATE messages transmission).  The impact of including
an additional BGP message type for such operational visibility is
relatively small from a resource utilisation perspective - additional
processing overhead is only experienced when such a message is
received.  Where a separate session is maintained, particular network
elements within a service provider topology may require hundreds, or
thousands, of additional sessions for the transmission of this
information.  Such an resource consumption overhead is likely to be
unacceptable to some network operators.
For the reasons explained above, it is expected that mechanisms
specified to meet the requirements for event visibility consider the
relative impacts of additional monitoring sessions, or message
inclusion in band to BGP in order not to compromise the security,
scalability and robustness of the BGP-4 protocol.
7.  Operational Complexities Introduced by Altering RFC4271
The existing NOTIFICATION and subsequent teardown of a BGP session
upon encountering an error has the advantage that a consistent
approach to error handling is required of all implementations of the
BGP-4 protocol.  This is of operational advantage, as it provides a
clear expectation of the behaviour of the protocol.  The requirements
defined herein add further complexity to the error-handling within
BGP, and hence are liable to compromise the existing deterministic
protocol behaviour.  It is therefore deemed that there is a further
requirement to provide a clear method by which an erroneous UPDATE
should be reacted to, in order that all protocol implementations
provide a consistent means by which recovery is achieved.  A further
complexity is introduced due to the disparate nature of the work
items altering the BGP error handling behaviour - since all items are
likely to be implemented as a BGP capability [RFC5492], situations
are likely to occur between devices (especially those with different
BGP implementations), where some of the mechanisms referenced are
unsupported.  This adds further barriers to a standard definition of
the BGP-4 error handling behaviour.
In general, the approach considered ideal upon encountering an
erroneous UPDATE message can be divided into two cases - those where
the NLRI can be determined from the message, and those where it
cannot be.  The latter case is the simpler of the two.  In this case,
there is a requirement for the implementation to reset the BGP
session, utilising the reduced-impact approach, described in
Section 5.  In the case where the remote BGP speaker is in a
transient error condition related to specific peer data structures,
or state, a single instance of this behaviour is likely to exit the
error condition.  In the case of implementation errors, it is
possible that the BGP session in question may enter a continuous loop
of being reset, with a partial RIB being held by one or more of the
BGP speakers due to an non-deterministic order of UPDATE propagation.
It is therefore a requirement that within this reduced-impact
procedure any subsequent UPDATE messages that would result in further
session resets are ignored.  Whilst this results in a condition where
an undetermined amount of the RIB is inconsistent, partial
reachability is maintained.  In this case, the operational toolsets
discussed in Section 6 is likely to provide mechanisms by which this
condition can be brought to the attention of the relevant operators.
This requirement to accept a partial RIB, which results in potential
invalid traffic forwarding is a direct result of the deployments of
BGP-4, as described in Section 1.1.
The case where NLRI can be determined from an erroneous UPDATE
provides further complexities.  In this case, a BGP speaker is aware
of the sub-set of the RIB which have been identified as being
contained within invalid UPDATE messages.  This allows a local BGP
speaker to re-request single prefixes, utilising a mechanism such as
"one-time prefix ORF".  However, a similar result is achieved by re-
requesting the entire RIB - albeit with greater resource
requirements.  It is therefore expected that the process of recovery
utilises a staged set of mechanisms to attempt to restore consistency
of the RIB:
1.  Where available, a mechanism capable of requesting only the NLRI
determined to have been contained within a invalid UPDATE should
be utilised.  However, since it is possible that such an error
condition can be transient in nature, it is likely that more than
one request is to be transmitted (assuming the first does not
return a valid UPDATE message).  In order to allow a
deterministic process, there is a requirement for a limit on the
number of specific requests transmitted to be defined.
2.  Where a specific refresh mechanism is not available, a peer
should re-request the entire RIB.  Again, there is a requirement
to limit the number of complete RIB requests that should be sent
via an implementation, in order to provide a bound both on the
expected level of load a device may experience, and on the time
for which the RIB may be inconsistent.
3.  Finally, a session reset should be performed, as per the reduced-
impact NOTIFICATION requirement defined in Section 5.  At this
point, a similar challenge to that discussed above exists, should
the error condition persist.  In this case, as defined above,
there is a requirement to ignore those UPDATE messages that
continue to be erroneous.
It is envisaged that where limits are required, these will be defined
on a per memo-basis, or within a further revision of the requirements
described herein.
Whilst the approach described above provides a standard means by
which error recovery may be handled on a per UPDATE basis, further
complexities are raised where multiple errors occur.  Clearly,
following this procedure causes control-plane load on both the BGP
speakers - for this reason, consideration of how repeated use of the
mechanisms discussed in this document is required.  It is notable
that errors may not occur with UPDATE messages relating to only a
single NLRI, independent errors in multiple NLRIs may be experienced.
For this reason, it is required that an implementation rate limits
the number of error handling events sourced towards a particular
neighbour.  It is expected that such rate limiting, or event
suppression is achieved on a per-session basis, where state
information is already held, rather than on a per-prefix basis as it
is envisaged that such behaviour presents significant scaling
problems, and introduces further state requirements for an
implementation of the protocol.  It is recommended that where a flag
indicative of erroneous behaviour is implemented, the state of such a
value is maintained independently of session establishment.
7.1.  Reducing the Network Impact of Session Teardown
In some cases, where repeated erroneous UPDATE messages are received
on a BGP-4 session, it is desirable that a BGP speaker disconnects
completely from the remote peer without performing a restart, in
order to avoid the control-plane overhead of repeated session
establishment, and subsequent reset events.  This behaviour may be
required after a per-session flag indicating erroneous behaviour is
set, as discussed in Section 7.  The BGP-4 specification presented in
[RFC4271] achieves such a session shutdown by sending a NOTIFICATION
message, however, this has the net result that all downstream BGP
speakers (i.e. those to whom the NLRI carried over the now ceased BGP
session was readvertised) must withdraw this NLRI from their RIB, and
perform a best-path selection if required.  In some cases, there may
be no alternate path being available, and hence a period of time for
which no valid BGP route exists.  Particularly, this is very likely
to occur where an upstream BGP speaker performs a best-path selection
and advertises only a single path to its neighbours - there is a
requirement for the upstream speaker to perform a best-path
selection, and re-advertise a new set of NLRI before the downstream
system is able to converge to a new path.  It should be noted that
where UPDATE messages withdrawing NLRI are not subject to the BGP
session's configured MinRouteAdvertisementInterval (MRAI) [RFC4271],
but re-advertisements are, this may result in a BGP speaker being
without a path for a period up to the MRAI.
Clearly, it is advantageous to avoid this period of time for which
there may be no reachability for a set of NLRI, especially since the
BGP speaker terminating a particular session is doing so due to a
particular error handling policy.  The graceful shutdown mechanism
detailed in [I-D.francois-bgp-gshut] provides a mechanism by which a
BGP speaker is able to signal that a set of NLRI is to be withdrawn,
and hence allow downstream systems to pre-emptively perform a best-
path selection, and hence advertise new reachability information in a
make-before-break manner.
It is therefore envisaged, that where a session is to be shutdown,
based on a trigger relating to erroneous UPDATE messages being
received (be they repeated or not) that the graceful shutdown
procedure in utilised, so as to reduce the forwarding impact of NLRI
received on the session being withdrawn.
This memo includes no request to IANA.
The requirements outlined in this document provide mechanisms by
which erroneous BGP messages may be responded to with limited impact
to forwarding operation.  This is of benefit to the security of a BGP
speaker in general.  Where UPDATE messages may have been propagated
by a single malicious Autonomous System or router within a network
(or the Internet default free zone - DFZ), which are then propagated
to all devices within the same routing domain, all other NLRI
available over the same session become unreachable.  This mechanism
may provide means by which an Autonomous System can be isolated from
required routing domains (such as the Internet), should the relevant
UPDATE messages be propagated via specific paths.  By reducing the
impact of such failures, it is envisaged that this possibility may be
constrained to a specific set of NLRI, or a specific topology.
Some mechanisms meeting the requirements specified in this document,
particularly those within Section 6 may provide further security
concerns, however, it is envisaged that these are addressed in per-
enhancement memos.
The author would like to thank the following network operators for
their insight, and valuable input in defining the requirements for a
variety of operational deployments of the BGP-4 protocol; Shane
Amante, Bruno Decraene, Rob Evans, David Freedman, Tom Hodgson, Sven
Huster, Jonathan Newton, Neil McRae, Thomas Mangin, Tom Scholl and
Ilya Varlashkin.
In addition, many thanks are extended to Jeff Haas, Wim Hendrickx,
Alton Lo, Keyur Patel, John Scudder, Adam Simpson and Robert Raszuk
for their expertise relating to implementations of the BGP-4
11.  References
11.1.  Normative References
[RFC2858]  Bates, T., Rekhter, Y., Chandra, R., and D. Katz,
"Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.
[RFC2918]  Chen, E., "Route Refresh Capability for BGP-4", RFC 2918,
[RFC4271]  Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4364]  Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006.
[RFC4456]  Bates, T., Chen, E., and R. Chandra, "BGP Route
Reflection: An Alternative to Full Mesh Internal BGP
(IBGP)", RFC 4456, April 2006.
[RFC4724]  Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y.
Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724,
[RFC4760]  Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760,
[RFC5492]  Scudder, J. and R. Chandra, "Capabilities Advertisement
with BGP-4", RFC 5492, February 2009.
11.2.  Informational References
[I-D.chen-ebgp-error-handling]
Chen, E., Mohapatra, P., and K. Patel, "Revised Error
Handling for BGP Updates from External Neighbors",
draft-chen-ebgp-error-handling-01 (work in progress),
[I-D.francois-bgp-gshut]
Francois, P., Decraene, B., pelsser, c., and C. Filsfils,
"Graceful BGP session shutdown",
draft-francois-bgp-gshut-01 (work in progress),
[I-D.frs-bgp-operational-message]
Raszuk, R., Shakir, R., and D. Freedman, "BGP OPERATIONAL
Message", draft-frs-bgp-operational-message-00 (work in
progress), July 2011.
[I-D.ietf-grow-bmp]
Scudder, J., Fernando, R., and S. Stuart, "BGP Monitoring
Protocol", draft-ietf-grow-bmp-05 (work in progress),
[I-D.ietf-idr-optional-transitive]
Scudder, J. and E. Chen, "Error Handling for Optional
Transitive BGP Attributes",
draft-ietf-idr-optional-transitive-03 (work in progress),
[I-D.keyupate-idr-bgp-gr-notification]
Patel, K., Fernando, R., Scudder, J., and J. Haas,
"Notification Message support for BGP Graceful Restart",
draft-keyupate-idr-bgp-gr-notification-00 (work in
[I-D.keyur-bgp-enhanced-route-refresh]
Patel, K., Chen, E., and B. Venkatachalapathy, "Enhanced
Route Refresh Capability for BGP-4",
draft-keyur-bgp-enhanced-route-refresh-02 (work in
progress), March 2011.
[I-D.zeng-one-time-prefix-orf]
Zeng, Q. and J. Dong, "One-time Address-Prefix Based
Outbound Route Filter for BGP-4",
draft-zeng-one-time-prefix-orf-01 (work in progress),
[RFC5881]  Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881,
Rob Shakir
Cable&Wireless Worldwide
Email: rjs@cw.net
URI:   http://www.cw.com/


text:
Indian Super League (ISL)
Indian Sports Leagues
Other Languages 
AUS VS IND - stumps
ENG VS SRL - stumps
AUS VS IND - Completed
IRE VS UAE - Completed
PAK VS NZL - Completed
» No evidence against me, life ban imposed by BCCI unfair: Sreesanth tells SC
No evidence against me, life ban imposed by BCCI unfair: Sreesanth tells SC
Published: Wednesday, February 27, 2019, 20:30 [IST]
oi-Chitrangada Dc
New Delhi, February 27: Banned cricketer S Sreesanth claimed in the Supreme Court on Wednesday that BCCI's decision imposing life ban on him was "completely unfair" and Delhi Police "continuously tortured" him in custody to extract confession of his involvement in the 2013 IPL spot-fixing scandal.
Sreesanth, who was arrested and later discharged by a trial court here in July 2015 in a criminal case related to the alleged spot-fixing, claimed he had to confess his involvement in the alleged crime as police tortured him in custody and threatened to implicate his family in the case.
The 35-year-old cricketer has challenged in the top court the decision of a division bench of the Kerala High Court which had restored the life ban imposed on him by the Board of Control for Cricket in India (BCCI). His counsel told a bench of justices Ashok Bhushan and K M Joseph there was "no clear proof" and evidence of match fixing and Sreesanth has suffered a lot in the past five-six years.
"In the context of facts and manner in which these things have happened, this court should consider that it (life ban on Sreesanth by BCCI) is unfair. He has suffered for last five-six years. People want him to play cricket. He was extremely loyal to BCCI," senior advocate Salman Khurshid, appearing for Sreesanth, told the bench.
Khurshid said it was not established that any spot-fixing was done in the match played between Indian Premier League teams Rajasthan Royals and Kings XI Punjab in Mohali in May 2013 and there was no evidence that the cricketer received any money for this.
"The team (Rajasthan Royals) and its owners were banned for two years only. It is completely unfair that this (life ban) has happened with him (Sreesanth)," Khurshid said.
On the issue of his confession before police about his involvement in the alleged crime, the lawyer said, "The confession was due to continuous torture by Delhi Police. According to Sreesanth, police had threatened to implicate his family if he does not confess to the crime."
Khurshid argued the "standard of proof" against Sreesanth was nothing compared to the serious allegations levelled against him and the recorded telephonic conversations were not provided to him during the inquiry proceedings by BCCI's disciplinary committee.
Referring to the recorded telephonic conversations, he said there was no evidence to substantiate the claim that Sreesanth had received money for conceding 14 runs in an over during the IPL match in Mohali. Khurshid argued that as per allegations, Sreesanth was supposed to concede 14 runs in an over but he gave away 13 runs and the commentary during the match clearly reflected he had not bowled loose deliveries in that over.
He said it was alleged that Sreesanth tucked a towel in his trouser to give indication to bookies before the start of the over but the fact was he had used towel during matches since 2009.
The lawyer argued that Sreesanth used towel during the match as weather was humid in Mohali and he was using the towel to wipe out sweat from his palm which is usual for bowlers. Khurshid said nowhere in the world, life ban has been imposed on a cricketer like this. He said life ban was imposed on former Indian captain Mohammad Azharuddin, who was accused of being involved in a match-fixing scandal in 2000, but it was overturned later.
On November 8, 2012, the Andhra Pradesh High Court had termed the life ban imposed by the BCCI on Azharuddin as illegal and said it was unsustainable in law. Similarly, Khurshid said life ban was imposed on former South African captain Hansie Cronje but he died in 2002 in a plane crash.
He also referred to the case of former Indian cricketer Ajay Sharma and said the life ban imposed on him for his alleged role in a match-fixing scandal was later lifted. He also referred to the cases of ban imposed on several international cricketers, including Mohammad Amir, Salman Butt and Danish Kaneria, Herschelle Gibbs, Mohammad Ashraful and Lou Vincent for their alleged roles in fixing matches.
Khurshid said the recorded telephonic conversations did not show that the Mohali match was fixed in any way and evidence produced by police was not accepted by the trial court. The top court has posted the matter for hearing on Thursday when counsel appearing for Committee of Administrators (CoA) of BCCI would advance his arguments.
Sreesanth had told the top court that he has offers to play English county matches and the life ban imposed on him by BCCI is "too harsh". The apex court last year asked the Delhi High Court to decide expeditiously the appeal filed by Delhi Police challenging a trial court order discharging several accused, including Sreesanth.
Delhi Police had arrested Sreesanth, along with cricketers Ajit Chandila and Ankeet Chavan, and others on charges of spot-fixing. As many as 36 accused in the spot-fixing case, including Sreesanth, Chavan and Chandila, were discharged by a trial court here in July 2015.
The BCCI, however, had refused to alter its disciplinary decision of life ban on Sreesanth even after the trial court's verdict. A single-judge bench of the Kerala High Court had lifted the life ban imposed on Sreesanth by BCCI and had set aside all proceedings against him initiated by the board. Later, a division bench of the high court had restored the ban on a petition filed by the BCCI against the single-judge bench's order.
More S SREESANTH News
Syed Mushtaq Ali Trophy 2021 | Sreesanth retruns to the field with fire and passion
Syed Mushtaq Ali T20 tournament: Sreesanth in Kerala team, Sanju Samson to lead the side
Sreesanth named in Kerala probables list for Syed Mushtaq Ali Trophy
Sreesanth set to play in KCA President's Cup T20 post ban
IPL 2020: Sanju Samson doesn't need to be next anyone: Gautam Gambhir's retort to Shashi Tharoor's tweet
S Sreesanth expresses relief as IPL spot-fixing ban ends, pledges 'to give it all' to any team he plays for
Chavan writes to BCCI, MCA to reconsider his life ban
SportsTiger launches 'Off-The-Field' - an exclusive weekly interview series
MS Dhoni retirement: S Sreesanth explains what could be the ideal moment for former India captain's swansong
With Michael Jordan's former trainer for help, Sreesanth readies for redemption
Sreesanth is still sharp as a bowler at nets, says Kerala teammate Sachin Baby
Excited at the opportunity, says Sreesanth after path opens for Ranji Trophy return for Kerala
Get breaking news alerts.
ISL 2020-21: JFC vs NEUFC: NorthEast end winless streak to bag crucial points against Jamshedpur
13 min ago Public outcry in Greece after Olympic medalist opens up about sexual assault
21 min ago ISL 2020-21: JFC vs NEUFC: NorthEast end winless streak to bag crucial points against Jamshedpur
1 hr ago Coronavirus: Australian Open confirms further 25 players are quarantining
2 hrs ago India vs Australia: We faltered in execution, admits Josh Hazlewood
News Wuhan scientists admit to being bitten by COVID-19 infected bats
Love Cricket? Prove it! Play myKhel Fantasy Cricket here
Read more about: s sreesanth bcci ban ipl spot fixing supreme court cricket
Story first published: Wednesday, February 27, 2019, 20:30 [IST]
Other articles published on Feb 27, 2019
Find the best IPL odds at 10Cric! Bet on all matches directly from your mobile phone.
Play casino in India at 7Jackpots, and enjoy real money games with fast and secure withdrawal options.
Imran Khan and Virat Kohli: Who is the best player as captain?
Mohammed Siraj racial abuse row: Won't be tolerated says Rahane
Virender Sehwag shares an emotional video, says 'Insaaniyat Zindabad':Watch
Mohammed Siraj gets emotional as National Anthem plays
Sourav Ganguly discharged from Kolkata hospital after 5 days after angioplasty
4th ODI
Jan 18 2021, Mon - 11:00 AM
1st ODI
Jan 20 2021, Wed - 01:30 PM
Jan 21 2021, Thu - 11:00 AM
3rd Test
338, 312/6 decl
244, 334/5
United Arab Emirates won by 6 wickets
659/6 decl
New Zealand won by an innings and 176 runs
Home | RSS Feeds | Coupons | Facebook | Twitter | Sitemap | Feedback | Advertise with us | About Us | Contact Us | Cookie Policy
© 2021 myKhel. All rights reserved. | Terms of Service and Privacy Policy


Garage door weather seal complete kit for garage doors up to 9. Genie garage door opener gear kit replacement complete kit all. Garage door torsion spring conversion kit flawless garage door. Advanced plastic garage door threshold complete diy kit with glue.


text:
L' è un tipo di wagashi (un dolce tradizionale giapponese) a base di azuki o altri tipi di fagioli ricoperti con una glassa di zucchero.

Storia
L'amanattō fu sviluppato da Hosoda Yasubei nell'era Bunkyū (1861-1863) del periodo Edo, quando aprì a Tokyo un negozio di wagashi (ancora esistente), che battezzò con il suo nome d'infanzia, Eitaro.

Originariamente l'amanattō si chiamava ; il nome è stato abbreviato dopo la seconda guerra mondiale. La somiglianza con il nome del piatto di fagioli di soia fermentati nattō è solo una coincidenza.

A Hokkaidō l'amanattō viene utilizzato per preparare il sekihan in quanto, a differenza di quanto avviene in altre regioni, il piatto è leggermente dolce.

Note

Wagashi
Dolci a base di fagioli


Title: Tulipomania Author: Wilfrid Blunt Type: Non-Fiction Page Count/Review Word Count: 50 Rating 4/5 This was a first edition King Penguin book, and it was beautiful. As well as containing interesting information on the history of tulips, it also contains some beautiful illustrations. It's awesome. Click here to buy Tulipomania.


Leadership Resources for all, executives, managers, aspiring leaders, Confidence, Resilience, Mental Toughness, Leadership Coaching, Executive Coaching, Leader Development, ILM Development Programmes, Business Coaching, Personal Coaching, & Training.
Here is how to solve a million-dollar problem that every leader faces, with simple yet powerful leadership practices that you can implement immediately.
According to Gallup (2013), only 13% of employees worldwide are engaged, and a quarter of employees report that they are actively disengaged. The costs of this situation are staggering in terms of lost productivity and the cost of replacing people. The value of high engagement is enormous – the Gallup research shows organisations with highest engagement are 22% more profitable than organisations with low engagement. They also have higher productivity, customer satisfaction, and retention of key people.
How to engage, motivate and mobilise your people is a top frustration for many leaders of both large and small organisations.
They are tired of spending so much time dealing with the fallout that comes from people who are not as committed and motivated as they are. Symptoms multiply - lack of time, deadlines missed, budgets exceeded, constant firefighting, some team members not pulling their weight, and more.
The answer might be simpler than you think…. You probably don't need to re-write all your systems and processes, sack everyone (or particular troublemakers) and recruit a whole new team. While there is no magic solution, there are simple yet powerful leadership practices you can do that cost nothing to implement and can produce immediate improvements in performance. All you need is to know what they are and how to implement them! Sue can help you achieve this, with an 11-part methodology you can use yourself and also with your leadership team to address the problems of employee engagement. Best of all, this methodology doesn't require invasive organisational development strategies or restructurings that are almost impossible to implement. Instead, we focus on simple but powerful behaviours that have maximum impact on your leaders' ability to engage and motivate their people.
Would it be relevant for you?
To learn more, we invite you to take the Engagement self-assessment.
How can great leadership add value for you?
What is the value for your organisation?
What is the value for you personally?
Contact Aeona today to see how our programmes will benefit you.
for a no obligation chat or to arrange a strategy session.


Love It? Not so good! Not that bad! It's OK! Like It! Love It!
Join us every Friday at McGettigan's Souk Madinat Jumeirah and enjoy our a brand new offer: Brunch & Tonic!
From 12.30pm until 4.30pm, guests can enjoy a mix of unlimited a la carte dishes as well as succulent roasts from a live carvery station and buffet featuring salads, soups, seafood and desserts.
Choose between either a soft drinks, house drinks, or a premium beverage package which includes sparkling Brut, house drinks, cocktails and a fabulous selection of gins.
not to mention new guest gins added each week!
Stay on for more Friday fun with our Fri-YAY Post Brunch Drinks Package just AED 210 per person from 5pm until 8pm.
Every Friday from 12.30pm until 4.30pm.
I have been to this place.
Your review is being published. Please Wait.
Simply enter in your email and get the best promos delivered to your inbox every week!
Copyright © PromoLover, a division of 549 Media. All Rights Reserved.


Social media marketing arguably has become a life line for businesses around the world to grow leaps and bounds. Last few decades have witnessed how companies leveraged the inherent power of social media marketing tools to widen their business growth avenues. No matter if it's a decade old company or an ambitious start-up, social media marketing tools promise to pitchfork businesses to a consolidated position in the perpetually growing competitive market. Contrary to the traditional marketing gimmicks, active presence in myriad social media platforms has become a popular and preferred strategic choice.
For companies to develop a strong foothold in the highly volatile social media platforms, well thought-out strategies have become essential to increase social media views of its sought after products. There are various social media marketing tools that help businesses to attract and engage customers in an impressive business proposition with the company.
1. Enhanced brand recognition: With growing presence of company products and services on various social media platforms, the otherwise passive consumers are likely to grow more inquisitive about what all the company has to offer, perhaps to address their concerns. Also, companies continuously improve upon their social media marketing tactics to increase social media views through frequently used social media sites.
Increased reach to potential consumers: With extended presence to other social media marketing tools such as Instagram, companies have developed the competencies to increase Instagram followers by regularly updating photos and other images. Additionally, companies can make use of google plus posting to allow potential users of the products or services to come together and interact in community circles. Companies strive hard to increase google plus circles so that a diverse consumer market could be attended to. By posting video updates regularly, companies could potentially increase you tube views to increase traffic to their website. Instead of barging with ill-designed tweets, companies should focus to increase twitter followers via targeted tweets.
2. Reduced marketing efforts: Unlike the traditional marketing schemes, social media marketing comes out quite handy for companies. They primarily extend their strategic vision to expand their social media presence so as to attract and engage customers for life time.
With such irrepressible buzz around social media marketing to grab a meaty share of the consumer market, there lies a huge onus on social media company to drive money minting mechanisms for companies through effective social media marketing tools. While some may call it 'overhyped', and downplay it as a passing fad, there is absolutely nothing that contradicts the alluring moolah that companies can rake in, albeit with astute strategic planning.
One Response to "Positive effects of social media marketing in business"
Yes it is true that social media is helpful the writers can also advertise their talent on social media so they will attract more users.