text:
Neal Schon's 2011 Journey live rig in pictures
"My set-up is so simple... there's nothing to it"
Guitarist recently caught up Journey's Neal Schon on the band's European tour and alongside an in-depth interview (buya digital edition of issue 344 to find out what Schon had to say), we couldn't resist a look at his impressive live rig.
"My set-up is so simple... there's nothing to it" claims Schon, in the understatement of the year. Click onwards to check it out...
Schon uses just one of his three Blackstar amps – alongside a trio of 4 x 12 S1-412B cabs – and he then runs the dry signal into his current favourite piece of kit, the rack-mount Fractal Axe-FX Ultra.
"It's light years beyond anything I've played," he beams. "It's loaded, man. It's a processor, but it doesn't sound or react like a processor. I've been able to get any sound I want out of it. [One of my favourites] is a brown-sounding Marshall with the mic away from the speakers just a bit."
Other rack equipment includes Gibson's Echoplex Digital Pro, the Roland M-120 Line Mixer and Fantom XR, plus the Lectrosonics R400A Dual Receiver.
Neal's pedalboard includes three FV-300L volume pedals, EV-5 Synth and Compression Sustainer (all Boss), the EWS FD-1 Fuzzy Drive and Wampler's Nirvana Chorus.
These days, he stresses , it's more about quality of tone than mindless blasting. "Stage volume is way down," he concludes. "You don't need it to go warrghh! I don't want people's ears to bleed or their hair to blow back…"
Echoplex foot controller
Alongside his pedalboard, Schon uses the Echoplex foot controller - complete with gaffer tape - to trigger delay effects.
Customised PRS Singlecut
After jumping ship to PRS from Gibson, Neal's gigging workhorse is now a customised 22-fret PRS Singlecut madefrom mahogany and curly maple, with a Floyd Rose vibrato, DiMarzio Fast Track (with sustainer) in the neck and '57 Plus at the bridge.
"I have one guitar technician in San Francisco who does all my work," he notes. "This guitar is like a giant Ebow! I like Seymour Duncans in the studio, but onstage, I find them a little oinky, so I'll go for a more straightforward '58 or '57 PAF. I don't get output out of the guitar as much live, I punch the amps more."
Custom PRS doubleneck
With 18 strings and a Floyd Rose vibrato on this beauty, all we can say is that we're glad we aren't his guitar tech!
Fender Custom Shop Stratocaster
When it comes to playing Lights, or other classic Strat-powered Journey moments, Schon turns to this rather lovely sunburst example.


text:
ROME – A witness in the Costa Concordia shipwreck trial has described how the captain jumped aboard a lifeboat, testifying how the commander wasn't the last to abandon the rapidly capsizing luxury cruise ship.
Francesco Schettino, the captain, is being tried in Tuscany for alleged manslaughter, abandoning ship and causing the shipwreck near the Tuscan island of Giglio in January 2012. Thirty-two people died in the capsizing.
Stefano Iannelli, crewman-in-training, testified Monday that Schettino jumped, shortly before he himself did, onto the roof of a lifeboat. Iannelli said he didn't see any passengers still aboard. However, hours after Schettino abandoned ship, helicopters rescued people from the capsized vessel.
Iannelli said the Concordia was listing so badly that crew formed a human chain to avoid falling while they helped people.

subset: commoncrawl


text:
Australian English decidedly finds its origins in British English. But when it comes to chasing down Irish influence, there are – to paraphrase Donald Rumsfeld – some knowun knowuns, some unknowun knowuns, and a bucket load of furphies.
Larrikins, sheilas and Aboriginal Irish speakers
The first Irish settlers, around half of whom were reputedly Irish language speakers, were viewed with suspicion and derision. This is reflected in the early Australian English words used to describe those who came from Patland (a blend of Paddy and Land).
The Irish were guided by paddy's lantern (the moon); their homes adorned with Irish curtains (cobwebs); and their hotheadedness saw them have a paddy or paddy out. These Irish were said to follow Rafferty's Rules – an eponym from the surname Rafferty – which meant "no rules at all".
More than a few Irish were larrikins. In his book Austral English, E.E. Morris reports that
in 1869, an Irish sergeant Dalton charged a young prisoner with "a-larrr-akin about the streets" (an Irish pronunciation of larking, or "getting up to mischief"). When asked to repeat by the magistrate, Dalton said: "a larrikin, your Worchup".
This Irish origin of larrikin had legs for many years, and perhaps still does. Unfortunately, here we have our first furphy, with more compelling evidence linking larrikin to a British dialect word meaning "mischievous or frolicsome youth".
But if larrikin language is anything to go by, these youths went way beyond mischievous frolicking – jump someone's liver out, put the boot in, stonker, rip into, go the knuckle on and weigh into are just some items from the larrikin's lexicon of fighting words.
Read more:
Future tense: how the language you speak influences your willingness to take climate action
With the Dalton furphy, though, we see evidence of something called "epenthesis", the insertion of extra sounds. Just as Dalton adds a vowel after his trilled "r" in a-larrr-akin, many Aussies add a vowel to words like "known" and "film" (knowun and filum) – and here we see a potential influence of the Irish accent on Australian English.
In contrast to larrikin, the word sheila is incontrovertibly Irish. Popular belief derives it from the proper name, Sheila, used as the female counterpart to Paddy, a general reference to Irish males.
Author Dymphna Lonergan, in her book Sounds Irish, prefers to derive it from Irish Gaelic síle, meaning "homosexual", noting Sheila wasn't a particularly popular Irish name as it began to appear down under.
Significantly though, St Patrick had a wife (or mother) named Sheila, and the day after St Paddy's Day was once celebrated as Sheelah's Day. So, Sheila was something of a celebrity.
Barrack is another likely Irish-inspired expression. A range of competing origins have been posited for this one, including the Aboriginal Wathawarung word borak, meaning "no, not", and links to the Victorian military barracks in Melbourne.
But the most likely origin is the Northern Irish English barrack, "to brag, be boastful of one's fighting powers". The word has since sprouted opposite uses – Australian barrackers shout noisy support for somebody, while British barrackers shout in criticism or protest.
Perhaps surprisingly to many, the Irish were the first Europeans some Australian Aboriginal tribes encountered.
This contact is evident in the presence of Irish words in some Aboriginal languages. For instance, in the Ngiyampaa language of New South Wales, the word for shoe is pampuu, likely linked to a kind of shoe associated with the Aran Islands in Ireland, pampúta.
Didgeridoos, chooks and shouts: An Irish language perspective
Lonergan argues that more attention should be directed to this sort of Irish Gaelic influence.
Lonergan points, for example, to archival evidence linking the origin of didgeridoo to an outsider's perception of how the instrument sounds, questioning the degree to which the sound corresponds to the word.
As a counter-argument, she notes an Irish word dúdaire meaning "trumpeter or horn-blower", as well as Irish and Scots-Gaelic dubh, "black" and dúth, "native". She observes that Irish and Scots-Gaelic speakers first encountering the instrument might well have called it dúdaire dubh or dúdaire dúth (pronounced respectively "doodereh doo" or "doojerreh doo").
Read more:
The origins of Pama-Nyungan, Australia's largest family of Aboriginal languages
Similar arguments are made for a number of other words traditionally viewed as having British English origins.
The Australian National Dictionary sees chook (also spelled chuck) as linked to a Northern English/Scottish variation of "chick". However, Lonergan notes this is phonetically the same word (spelled tioc) the Irish would have used when calling chickens to feed (tioc, tioc, tioc).
Another potential influence also comes from the transference of Irish meaning to English words. For example, the Australian National Dictionary is unclear as to the exact origin of shout, "to buy a round of drinks", but Lonergan links it to Irish working in the goldfields and an Irish phrase glaoch ar dheoch, "to call or shout for a drink".
Lonergan posits that Irish miners translating to English might have selected "shout" rather than "call" – "shouting" could easily have spread to English speakers as a useful way to get a drink in a noisy Goldfields bar.
Good dollops of Irish in the melting pot
Irish influence on Australian English is much like the influence of the Irish on Australians themselves – less than you'd expect on the surface, but everywhere once you start looking.
And those with a soft spot for Irish English might feel better knowing that some of their bête noires are in fact Irish (haitch, youse, but, filum and knowun).
As Irish settlers entered the Australian melting pot, so too did a hearty dose of their language.
Howard Manns, Lecturer in Linguistics, Monash University and Kate Burridge, Senior Fellow at the Freiburg Institute for Advanced Studies and Professor of Linguistics, Monash University
This article is republished from The Conversation under a Creative Commons license. Read the original article.


text:
Brand: KingTo
Color: A2-grey
- Foldable, you can fold it when you don't use it,Very perfect organizer for saving your room space.
- Adaptable for all types closet, maximum utilization of vertical space, it can be split into 2 closet organizer which making it perfect for small closets. It also has added mobility with a foldable design. Suitable for both home and travel, Easy to carry.
- It's convenient and 4 large enough pockets offer to store different items separately, store anything from adult handbag,shoes,purses,sweaters to baby clothing,toys.keep bags damage free.
- Easy to hang-Can be hang it in your wardrobe, closet or back door.
- Simple To Use for Dormitory, Classroom, Office, Workshop, Factory, Home, School.
Welcome to the "KingTo " shop , we will serve you faithfully!
◆Type: Hanging Bag
◆Material: Non Woven Fabric, PVC
◆Function: Bags and Other Accessories Storage
◆Features: Durable and Practical, Multi Pockets Design, Transparent Film, Double Side, Convenient.
-Very perfect organizer for saving your room space.
-Foldable: you can fold it when you don't use it.Can be hang it in your wardrobe, closet or back door.
-4 large enough pockets design, satisfied your different demand.
-Detachable,the middle part can be detached,and it will be 2 hanging bag.
-5 layer,the top layer can storage small bag.
-Applicable Scope: Clothing, Handbags, Lingerie, Bra etc.
what are you waiting? Don't you want to make your life more functional and easier?
Scroll Up And Click The "Add to Cart" Button NOW!Thank you very much for your browse.


text:
A Local Handyman In Reseda
Handyman: You've come to the correct place if you're looking for a handyman in Reseda, California. These professionals are frequently insured and have guarantee plans, so you don't have to be concerned about the quality of their work. They can handle a wide range of home repair needs, but they can also assist with a variety of tasks ranging from small house repairs to bathroom remodels.
Whether you need a handyman in Reseda to change a light bulb or fix a leaky faucet, a local handyman can assist you. These experts can also manage electrical and plumbing difficulties, as well as advise you on how to avoid a similar situation in the future. These pros can also perform repairs promptly and at a reasonable rate, so you won't have to worry about your home being wrecked.
If you have a project that is out of your budget, a Reseda handyman can help you out for a fair price. They can handle everything from a simple light bulb replacement to a major bathroom remodel. And because their services pose no big hazards, you won't have to worry about destroying your property or creating an accident. A handyman in Reseda can help with a variety of tasks and won't charge you an arm and a leg.
How Does A Handyman Put Together Furniture?
It is difficult to navigate home renovation stores like IKEA, and assembling furniture on your own necessitates physical labour and the right tools. If you have a lot of flat-pack furniture, hiring a handyman to put it together might save you a lot of time and effort. You can rely on a handyman to build your flat-pack furniture correctly and without error. You can also tip him according to how long it took him to do the project.
A handyman is well-equipped to assemble your flat-pack furniture and can ensure its durability. Most handymen who undertake this type of job demand a fixed minimum rate, and when charged by the piece, they do not account for the weight of each component. They have the necessary tools and time to properly assemble your flat-pack furniture. Even if you have explicit instructions, it is difficult to adhere to them.
A professional will also have experience with flat-pack furniture and may be able to explain the procedure to you as well as provide ideas on how to do it yourself.
How Does A Handyman Assist With Window Repair?
If you are unable to repair the broken window on your own, hiring a handyman for window repair may be an excellent option. These experts have greater qualifications and experience, but they also have specific training. A professional can handle and solve both short-term and long-term challenges. It would also be beneficial if you had a handyman to repair recurring issues with your windows, such as cracks or chipping.
When you hire a handyman to fix your windows, you need to know that the job will be done correctly the first time. He will evaluate the damage and make recommendations on the best course of action. If the damage is severe, he may advise you to replace the window. However, if the damage is modest, he can fix it fast. When handling broken glass, a handyman for window repair will wear heavy-duty gloves and transparent nail polish. He'll add clear tape to stop the crack from spreading after layering on clear nail paint.
What Is a Handyman's Role in Gutter Cleaning?
Hiring a handyman to clean your gutters is an excellent method to avoid the headache of doing it yourself. Cleaning your gutters is critical for preventing water damage to your home. Depending on the quantity of filth deposited, washing your gutters at least twice a year might be beneficial. The procedure might be complicated, and you will want specialised equipment and knowledge. If you have a hectic schedule, hiring an expert may be a better option.
You may have a handyman who can clean your gutters, or you may be able to do it yourself, but you must be sure that you are safe. Falling down a ladder can result in serious injuries, therefore you should be aware of how to avoid falls. Even if you don't live in an area where trees drop leaves, it's critical to get your gutters cleaned on a regular basis to avoid water damage.
Cleaning your gutters is an important element of house maintenance. To guarantee the safety of both you and your home, experts recommend hiring a handyman to clean your gutters.
Did You Hire A Reseda Licensed Electrician?
A handyman is an excellent choice for electrical repairs. He cannot, however, do anything on his own. If he does not do the work correctly, there is a good chance he may start a fire. The best course of action is to hire a professional electrician for the work. It is critical that the job be performed by a licenced electrician. This way, you can be confident that your electrical work is safe and up to code.
Unlicensed handymen should always be avoided when employing a handyman to conduct electrical repairs. These people may be inexperienced, making them dangerous on your property. They may also lack the necessary abilities to complete the assignment correctly, exacerbating the difficulty. Furthermore, if an electrical fire happens, you may be required to pay for insurance, which is an expensive hassle.
How Do You Rate The Reseda Handyman?
If you need some assistance around the house, you should seek local handyman reviews. It is always a better idea to spend some time researching numerous companies before settling on one. Other people may also provide you with beneficial suggestions and methods to help you save money on the repairs you need to do around the house. For example, if you need a window replaced, you may need to contact a local handyman.
Make sure to read internet reviews before hiring a handyman. There are several of them available, and you may choose the ideal one for your needs. A reputable handyman, such as Handyman Reseda, will have a long record of delighted clients and a reputation for quality work. A handyman should be able to estimate the cost of a project, as well as show you examples of their previous work.
When you find a good handyman in your region, you may decide whether or not to hire him. A handyman will typically charge a flat rate for a modest job that is cheaper than the cost of a larger one. A handyman may need to use a power tool for medium-sized work, which will generally take two to four hours to accomplish. Before hiring a handyman, consider the cost and the individual's experience. He will be able to help if he has prior experience in the field.
provide you a precise quote and show you examples of his work A Reseda Handyman will ensure that your property is in good hands in a comfortable, convenient, and cost-effective manner.
Brought to you by Handyman near me in Reseda, California
Handymanreseda Covers the Following Towns nearby Reseda, Los Angeles
Tarzana, Woodland Hills, Granada Hills, Mission Hills, Chatsworth, West Hills, Reseda,
The post What Does A Local Handyman do In Reseda, California appeared first on https://lonelyspooky.com
The post What Does A Local Handyman do In Reseda, California appeared first on https://wookicentral.com
The post What Does A Local Handyman do In Reseda, California appeared first on https://gqcentral.co.uk


text:
The 'New Normal' Is Here with 10 Chances to Win Cash – Up to $10,000 Right Now
So you're living in the "New Normal," making new ways to do life. That includes winning cash on KISS 106. We've been telling you it's coming, and your chance to play is happening right now.
Here's how we're defining the new normal: when we give you a chance to Win Cash, we're doing it better than ever by giving you 10 chances each day to win. We're paying out $1,000 twice each weekday and a grand prize of $10,000. The more codes you enter, the more chances you have to win.
Here's How It Works
- Do this right now: set your radio, download our app, or ask Alexa to listen to KISS 106 every weekday.
- We'll give you 10 codewords throughout the day - be sure to listen all day long, because we'll give you hints about when the next word is coming, too.
- Enter each word you hear on the KISS 106 app.
- We'll draw from all correct codeword entries and reward two $1,000 winners each day.
- One player will be randomly drawn for the biggest stimulus check anywhere, $10,000 - the more codes you enter, the better your chances.
Enter Your Winning Words Now
You've got at least one of the 10 words we gave you on-air today? Great! Enter them on the Win Cash contest page.
The easiest way to play is via our station app, get it at the link below.
Enter your number to get our free mobile app


text:
Let the great debate begin. On behalf of the "don't give him the money" position: Rules are rules, and the little guy needs to learn that sometimes there are disappointments in life. It's character-building. Let him slide this time and before you know it he'll be dealing drugs.
On behalf of the "c'mon" position: C'mon. C'mon.
Hurley lowered his head in defeat upon Trebek's pronouncement. Trebek then praised winner Skyler Hornback for his answer, which he noted was spelled correctly…
"I was pretty upset that I was cheated out of the final `Jeopardy!' question. It was just a spelling error," said the Newtown Middle School student, who won $2,000 as the second runner-up.
Until now a fan and regular watcher of the quiz show, Thomas said this episode cost "Jeopardy!" a fan. It likely has cost the show some adult fans, too.
The reply:
In an email, producers of Jeopardy! defended Trebek's decision.
"If 'Jeopardy!' were to give credit for an incorrect response (however minor), the show would effectively penalize the other players," they said. "We love presenting young people as contestants on our show and make every effort to be fair and consistent in their treatment."
The kid's from Newtown, Connecticut, for cripes sake. If he had spoken the answer, they'd have awarded him the money without question. C'mon.


text:
Not that it's any secret that state politicians are playing these games with our people and communities to their own advantage - the media here has been trying to tell folks about the private prison fiasco in AZ for awhile now, but people don't seem to listen or care. It scares me sometimes to think how much more stupid Arizona voters can still get about crime and punishment. If a politician says something will save taxpayer money and protect us from all the bad guys, our electorate will buy it even if it starves our own schools and poisons our own wells...which makes us look awfully cheap, vindictive, and just plain foolish.
Prisons, Privatization, Patronage
June 21, 2012
New York Times
By PAUL KRUGMAN
Over the past few days, The New York Times has published several terrifying reports
about New Jersey's system of halfway houses — privately run adjuncts to
the regular system of prisons. The series is a model of investigative
reporting, which everyone should read. But it should also be seen in
context. The horrors described are part of a broader pattern in which
essential functions of government are being both privatized and
First of all, about those halfway houses: In 2010, Chris Christie,
the state's governor — who has close personal ties to Community
Education Centers, the largest operator of these facilities, and who
once worked as a lobbyist for the firm — described the company's
operations as "representing the very best of the human spirit." But The
Times's reports instead portray something closer to hell on earth — an
understaffed, poorly run system, with a demoralized work force, from
which the most dangerous individuals often escape to wreak havoc, while
relatively mild offenders face terror and abuse at the hands of other
It's a terrible story. But, as I said, you really need to see it in the
broader context of a nationwide drive on the part of America's right to
privatize government functions, very much including the operation of
prisons. What's behind this drive?
You might be tempted to say that it reflects conservative belief in the
magic of the marketplace, in the superiority of free-market competition
over government planning. And that's certainly the way right-wing
politicians like to frame the issue.
But if you think about it even for a minute, you realize that the one
thing the companies that make up the prison-industrial complex —
companies like Community Education or the private-prison giant
Corrections Corporation of America — are definitely not doing is
competing in a free market. They are, instead, living off government
contracts. There isn't any market here, and there is, therefore, no
reason to expect any magical gains in efficiency.
And, sure enough, despite many promises that prison privatization will lead to big cost savings, such savings — as a comprehensive study by the Bureau of Justice Assistance,
part of the U.S. Department of Justice, concluded — "have simply not
materialized." To the extent that private prison operators do manage to
save money, they do so through "reductions in staffing patterns, fringe
benefits, and other labor-related costs."
So let's see: Privatized prisons save money by employing fewer guards
and other workers, and by paying them badly. And then we get horror
stories about how these prisons are run. What a surprise!
So what's really behind the drive to privatize prisons, and just about everything else?
One answer is that privatization can serve as a stealth form of
government borrowing, in which governments avoid recording upfront
expenses (or even raise money by selling existing facilities) while
raising their long-run costs in ways taxpayers can't see. We hear a lot
about the hidden debts that states have incurred in the form of pension
liabilities; we don't hear much about the hidden debts now being
accumulated in the form of long-term contracts with private companies
hired to operate prisons, schools and more.
Another answer is that privatization is a way of getting rid of public
employees, who do have a habit of unionizing and tend to lean Democratic
in any case.
But the main answer, surely, is to follow the money. Never mind what
privatization does or doesn't do to state budgets; think instead of what
it does for both the campaign coffers and the personal finances of
politicians and their friends. As more and more government functions get
privatized, states become pay-to-play paradises, in which both
political contributions and contracts for friends and relatives become a
quid pro quo for getting government business. Are the corporations
capturing the politicians, or the politicians capturing the
corporations? Does it matter?
Now, someone will surely point out that nonprivatized government has its
own problems of undue influence, that prison guards and teachers'
unions also have political clout, and this clout sometimes distorts
public policy. Fair enough. But such influence tends to be relatively
transparent. Everyone knows about those arguably excessive public
pensions; it took an investigation by The Times over several months to
bring the account of New Jersey's halfway-house-hell to light.
The point, then, is that you shouldn't imagine that what The Times
discovered about prison privatization in New Jersey is an isolated
instance of bad behavior. It is, instead, almost surely a glimpse of a
pervasive and growing reality, of a corrupt nexus of privatization and
patronage that is undermining government across much of our nation.


text:
Ted Nugent Says President Obama Represents 'Everything Bad About Humanity'
Getting Ted Nugent riled up about politics has become the reporting equivalent of shooting fish in a barrel, but when the Nuge sat down for an interview with the Broward-Palm Beach New Times recently, the writer couldn't resist — and Nugent was all too happy to oblige, taking the opportunity to go off on yet another tirade about what he sees as an epic struggle between good and evil.
Tossed the question, "If Romney were a rock band, what band would that be? Obama?," Nugent took the bait. Cautioning that "Out and out politicians are anathema to rock and roll, so I hesitate to attempt to connect the two," he nonetheless went on to add, "On important issues, I am saddened to admit that Obama represents everything bad about humanity and Romney pretty much all that is good. It is really that stark."
With that out of the way, Nugent next went on to discuss his involvement in Knife Rights, the self-described "Second Front in Defense of the Second Amendment" and "premier grassroots organization protecting our right to own knives." As Nugent argues, "The right to self-defense is secondary to the pure righteous instinct to self-defense. Historically, monster freedom-crushing tyrants, kings, emperors, despots, and evil slavedrivers denied mankind of such basic God-given rights, and this sacred experiment in self-government is based on refusing to give any of them up ever again."
"I saw the curse of apathy metastasize across this great country and the horrific attempt of evil politicians to infringe on these sacred rights through this increasingly opening door," he continues. "I decided early on that we the people have a moral bound duty to remain engaged and halt those daring to infringe.
"Freedom is not free and due diligence and vigilance is the only way to safeguard it," concluded Nugent, who would appreciate it if you practiced your diligence and vigilance with Ted Nugent brand bullets. "If a man is forced to be unarmed and helpless, you are at the mercy of evil, and that simply does not compute to conscientious, thinking people, so we stand and fight."


text: Latin Name : Pelargonium Graveolens.Part Of Plant Used : Leaves, Stalks & Flowers.Source : Egypt.Extraction Method : Steam Distillation.Geranium Essential Oil is steam distilled from the leaves and stalks of the plant Pelargonium odoratissimum (apple geranium). It has a strong smell with a floral aroma, and hints of mint and apple. The main feature of this oil is its ability to balance and uplift, and it is used to do both on the mind and body, to ease a host of ailments. Geranium essential oil helps balance oily and dry skin, and also brings about balance of the mind, relieving stress and anxiety. It is said to work on the adrenal cortex, which has a balancing effect on the hormone system. Geranium oil hasbeen used to treat acne, bruises, burns, cuts, dermatitis, eczema, haemorrhoids, ringworm, ulcers, breast engorgement, oedema, poor circulation, sore throat, tonsillitis, PMS, menopausal problems, stress, and neuralgia. Its strong smellchases away mosquitoes. Add a few drops to shampoo to get rid of head lice.These geraniums were believed to keep away spirits (like they did mosquitoes!) and so they were planted around houses as hedges. The plants originated from South Africa, Reunion, Madagascar, Egypt, and Morocco and were introduced to European countries in the 17th century. Although there are about 700 varieties of the plant, only 10 supply essential oil in viable quantities. The varieties planted in gardens usually produce too little oil to use for extraction.


text:
The AEM-7C is plug-compatible with the original HP 7900A drive, while using ARRAID's proprietary solid state 'ARRAID Flash Drive' (AFD) to store data. Internal AEM rotating drives (disk, tape & magneto-optic) can still be supported upon request.
No host system software or controller changes are required to replace a refurbished 7900A drive with the AEM-7C.
The AEM-7C provides a complete bridge between the host HP 13210 controller and the AEM's SCSI drives. These drives have been used on HP-1000 computers in a variety of applications. The HP 7900A is a combination fixed platter and removable cartridge drive of 5MB capacity.
While refurbished 7900A replacement drives have limited availability, refurbished drives commonly fail within a few months resulting in system down time. The AEM-7C is provided as new equipment, allowing customers to utilize SCSI drives or ARRAID's proprietary solid state 'ARRAID Flash Drive' (AFD) installed in the AEM-7C, with MTBF of 200,000+ hours and significantly more when using the solid state AFD.
Additional AEM-7C options include disk to disk backup, disk to tape backup, AFD network (backup & restore) mirroring, and multi-volume (provides several HP 7900A disk partitions on a single SCSI media). No refurbished HP 7900A drive can match the reliability, features and customer support provided by choosing the AEM-7C to replace your aging HP 7900A disk drive.
Contact Arraid today to learn more about new drive replacements for aging computer systems.
For More Information
Get the AEM-7C Data Sheet
Learn how the AEM-7C replaces HP 7900A disk drives using Disk Drive Emulation.
Unable to determine if the AEM-7C is right for your application? Contact us here or use Live Chat to speak with Arraid representatives.


text:
George Francis FitzGerald (1851-1901) was a prominent 19th century Irish physicist and a Member of the RDS. He is probably best remembered, along with Hendrik Lorentz, as a proposer of the first incomplete theory of relativity, The FitzGerald-Lorentz Contraction. Containing over 2,000 items of correspondence from some of the leading scientific figures of the period, the Fitzgerald Letters are a valuable resource for the study of 19th century science. In 2008 the RDS Committee of Science and Technology and the RDS Library & Archives collaborated on a project to digitize and catalogue the Fitzgerald Letters, which are now available here for the first time as a complete digital collection.
The RDS Art Collection comprises paintings, sculptures, prints and other objects which reflect the interests and activities of the RDS since it was established in 1731.
Digitisation of the artworks and objects in the RDS Art Collection is an RDS initiative funded by The Heritage Council


text:
Nebula Queen White Murphy Wall Bed and Gray Sofa
Items Included
- Sofa
- Wall Bed (mattress not included)
Make your wall bed even more functional by placing this sofa against it. The resulting wall bed/sofa combination is the perfect solution for making the most out of a very small space. It offers a place to sit, rest, lay down or sleep. Sit comfortably during the day, and when it's time rest, simply remove the cushions and fold out the Wall Bed.
When the bed is folded out, the sleeping surface fits perfectly over the seating area and between the armrests of the sofa. As a result, you can leave the frame of the sofa in place. When the bed is folded up, the sleeping surface becomes the backrest of the couch.
Sofa: The seat depth is 23.6" and its height is 17.4". The arm height is 4.7" above the seat. The arm width is 6" in. The interior width of each seat is 33".
Bed Unit: 78"W x 53.5"D x 89.1"H
- The bed when opened will require a clearance of 92.3" from the wall extending into the room.
- The minimum height required of the ceiling is 91 in.
- Clearance of 9.6" under the bed when it is open.
- Mattress not included.
- Accommodates most standard Queen mattresses. The mattress must meet the following requirements:
- The thickness between 20.3 and 30.5 cm (8 and 12 in).
- Weight between 27.2 and 40.8 kg (60 and 90 lb).
- Size of 203.2 cm (L) x 152.4 cm (W) (80 x 60 in).
- No futons.
- Box spring not required.
- QUALITY MATERIALS: Suspension is made with 9-gauge sinuous coils. Seat cushions are filled with non-glue cotton covered with D30 foam. 2" high plastic or chrome legs. Hardwood frame.
- SPACE-SAVER: The sofa and wall bed combination is the perfect solution for making the most out of your space. It offers both a place to sit and a place to sleep in very little space. To fold out the bed, simply remove the cushions and lower the bed.
- COMPATIBLE: The sofa can be used as an add-on to any of Bestar's Queen wall bed. Alternatively, it can be placed against a wall. You can choose either plastic or chrome legs.
- COMFORTABLE: The seat cushions are 7.9" thick. All fabrics have a heavy-duty backing. No nails are used, only staples.
- NOTE: Pre-assembled, except the legs. Overall dimensions: 78" W x 33.5" D x 39" H. 12-month limited warranty. Must be placed against a wall bed or a wall to support the back cushions. It can not be placed in the middle of a room since it does not have a backrest.


text:
Business gifts are not allowed as a tax deduction against profits. The legislation treats gifts in the same way as business entertaining expenditure, which is also disallowed.
HMRC define a gift as:
"… something that is given to a person without receiving anything in exchange. It is offered voluntarily and without any expectation of a return. An example of this would be gifts provided for potential customers who take a test drive in a new car – there is no obligation to buy the car and so nothing has been given to the trader in return for the gift.
Gifts may also arise where goods or services are supplied at less than the cost to the trader. For instance, a hotel might offer meals to its suppliers at a nominal charge. Here the difference between the cost of the meal and the price paid is a non-allowable gift. By contrast, if a baker reduces the price of fresh bread at the end of the day, this is a normal commercial transaction (as the bread will be worthless by the next day) and the cost is allowed in full."
Source: New feed


text:
What Would Bob Marley Look Like If He Was Alive Today?
Sadly, music legend Bob Marley passed away on May 11, 1981, of cancer at the age of 36. During his way-too-brief time as a recording artist, he released some of the greatest records ever made, including 1973's 'Catch a Fire,' 1974's 'Natty Dread' and 1977's 'Exodus.'
There's no telling where he may have taken his music if he was still alive today. But chances are pretty good he'd still be a significant artist. He not only helped make reggae a global powerhouse, he also shaped rock 'n' roll throughout the '70s.
And while there's also no way to tell what Marley would look like today, Sachs Media commissioned a company that creates photos for missing-persons reports by aging their subjects to draft a series of portraits featuring famous deceased rock stars.
One of the artists they worked their technological magic on was Marley, whose photo you can see above right. He doesn't look all that different. We're guessing his timeless music would have evolved a little more than the man himself over the past 30-plus years.


text:
150cm x 150cm
Original Artwork by Martin Breeze issued with a Certificate of Authenticity upon purchase.
The Artwork is Unframed as pictured, however framing is available in Black, White or Natural Finish and can be selected prior to checkout.
Please allow and additional 2-3 weeks required for framing. Also allow for 3cm increase to height and width of the original artwork dimensions to account for the frame size.
International Orders on Original Artworks will be shipped as a ROLL/TUBE to qualify for FREE Worldwide Shipping. The Artwork is carefully removed from the stretcher bars and shipped in a tube and can be stretched and framed in your local area reducing the risk of damage in transit. (Excludes Prints).
International Orders requesting Stretched or Framed Original Artworks will be quoted a shipping fee upon request. Please email email@example.com.
Damage to frames incurred during international shipping will not be refunded.
Breeze Creative will not be held responsible for any customs charges or taxes that may be incurred on international orders.
See T&C's page for more information on Shipping and Refunds/Returns
Stay in touch and I'll keep you up to date with New Exclusive releases.


text: Network Working Group E. Westheimer Request for Comments: 306 BBN NIC: 9257 February 15, 1972 Obsoletes: None NETWORK HOST STATUS This RFC reports on the status of most Network Hosts from January 31 to February 11. Several Hosts are currently excluded from the daily testing. These Hosts fall into two categories: 1) Hosts which are not expected to be functioning on the Network as servers (available for use from other sites) on a regular basis for at least two weeks. Included here are: NETWORK SITE COMPUTER ADDRESS 133 BBN PDP-10 (B) 13 Case PDP-10 15 Ames/(Paoli) ILLIAC/(B6500) 2) Hosts which are currently intended to be users only. Included here are the Terminal IMPs, which are presently in the Network (AMES, MITRE, NBS and BBN*). This category also includes the Network Control Center computer (Network Address 5) which is used solely for gathering statistics from the Network. Finally, included among these Hosts are the following: NETWORK SITE COMPUTER ADDRESS 7 Rand IBM-360/65 73 Harvard PDP-1 12 Illinois PDP-11 19 NBS PDP-11 The tables on the next two pages summarize the Host status for this period. ________ *The BBN Terminal IMP (Network Address 158) is a prototype and as such is frequently not connected to the Network, but being used to refine and debug the Terminal IMP programs. Westheimer [Page 1] RFC 306 Network Host Status February 1972 "STATUS OR SITE SITE COMPUTER STATUS OR PREDICTIONS" ADDRESS PREDICTION OBTAINED FROM 1 UCLA SIGMA-7 Server # Limited Jon Postel 65 UCLA IBM-360/91 NETRJS now Bob Braden (Telnet in April) 2 SRI(NIC) PDP-10 Server John Melvin 66 SRI(AI) PDP-10 SOON Len Chaiten 3 UCSB IBM-360/75 Server Jim White 4 UTAH PDP-10 Server Barry Wessler *5 BBN(NCC) DDP-516 Never Alex McKenzie 69 BBN(TENEX-A) PDP-10 Server Dan Murphy *133 BBN(TENEX-B) PDP-10 Server(Exper.) Dan Murphy 6 MIT(Multics) H-645 Server Mike Padlipsky 70 MIT(DM) PDP-10 Server Bob Bressler *7 RAND IBM-360/65 User only Eric Harslem 71 RAND PDP-10 Server Eric Harslem *8 SDC IBM-370/155 Server Bob Long 9 HARVARD PDP-10 Server Bob Sundberg *73 HARVARD PDP-1 User only Bob Sundberg 10 LINCOLN IBM-360/67 SOON Joel Winnet 74 LINCOLN TX-2 Server Will Kantrowitz 11 STANFORD PDP-10 SOON Andy Moorer *12 ILLINOIS PDP-11 User only John Cravits *13 CASE PDP-10 March Charles Rose 14 CARNEGIE PDP-10 SOON Hal VanZoeren 15 AMES/(PAOLI) ILLIAC September John McConnell (B6500) 16 AMES IBM-360/67 SOON Wayne Hathaway *144 AMES TIP User only *145 MITRE TIP User only *19 NBS PDP-11 User only Robert Rosenthal *147 NBS TIP User only *158 BBN TIP User only (Prototype) ________ * Host not included in daily testing. # The NMC is a research site and would like to have prior arrangement with each user. Westheimer [Page 2] RFC 306 Network Host Status February 1972 SITE SITE DATE AND TIME (EASTERN) NO. 1/31 2/1 2/2 2/3 2/4 2/7 2/8 2/9 2/10 2/11 1430 1530 1430 1630 1530 1830 1500 1730 1000 1230 1 UCLA-NMC H O O O O O O O O #D 65 UCLA-CCN O O O O D O O O D #D 2 SRI-ARC O O D O O O O T H O 66 SRI-AI D D D D D D D D D D 3 UCSB-MOD75 O O H O H D O O O O 4 UTAH-10 D O T O D D D O D D 69 BBN-TENEX T O O O O D O O O O 6 MIT-Multics O O D O O D R D O O MIT-DMCG H D D D D D H D O O 71 RAND-CSG T T T D D D D D T T 8 SDC-ADEPT #D #D #D #D #D D #D D #D #D 9 HARVARD O O O O #D #T O O D #D 10 L.L.-67 T H H D H D H H H H 74 L.L.-TX-2 D D D T T #D O #D D #T 11 SU-AI D D D D D D D D D D 14 CMU-10 D H H H H D D D D H 16 AMES-67 D D D D D D D D D D where D = Dead (Destination Host either dead or inaccessible [due to network partitioning or local IMP failure] from the BBN Terminal IMP.) H = 1/2 Open (Destination Host opened a connection but then either immediately closed it, or did not respond any further.) O = Open (Destination Host opened a connection and was accessible to users.) R = Refused (Destination Host returned a CLS to the initial RFC.) T = Time out (Destination Host did not complete the ICP and open a connection within 60 seconds.) ________ * The only service currently offered by the UCLA IBM-360/91 is a Network Job Service (NETRJS), however, the BBN Terminal IMP is not equipped to test NETRJS. We are assuming that initial connection to the NETRJS logger indicates that NETRJS is also functioning. Westheimer [Page 3] RFC 306 Network Host Status February 1972 # These sites advertise that they may not have their system available at these times. [This RFC was put into machine readable form for entry] [into the online RFC archives by Hélène Morin, Viagénie 10/99] Westheimer [Page 4]


text:
Regular price
Go with the flow in this BELLA + CANVAS lightweight, silhouette-flattering racerback tank. Ideal for Yoga class, summer months, going to the gym, or simply lounging around. Made from a soft poly-viscose blend, it is ideal for warm temperatures due to its flowy style. It's sure to be your new favorite tank!
- 7 oz., 65/35 polyester/viscose
- Side seams
- Tearaway label
- Ladies Fit


text:
Communicable and Environmental Diseases and Emergency Preparedness Weekly Reports
Annual Reports
The CEDEP Annual Report is designed to provide health care organizations and providers, government and regulatory agencies, and other concerned individuals and groups with important statistical information about potentially preventable diseases. The report can serve as one source of data for them and can help assure that involved individuals and organizations have access to reliable information. The annual report also provides an assessment of the efforts undertaken by CEDEP over a period of years.
To read an Annual Report, Select a year below:
Immunization Status Survey Of 24-Month-Old Children in Tennessee
An annual survey of the immunization status of 24 month old children is conducted by the CEDEP Immunization Program. The survey tracks progress toward achieving at least 90% on-time immunization with 10 routinely recommended vaccines.
To read annual survey results, select a year below:
Kindergarten Immunization Compliance Assessment
The annual Kindergarten Immunization Compliance Assessment evaluates immunization coverage and exemption levels of state-required vaccines among children entering kindergarten. The Tennessee Vaccine-Preventable Diseases and Immunization Program (VPDIP) collaborates with the Tennessee Department of Education (TDOE) to conduct this assessment of compliance with immunization requirements designed to ensure a healthy learning environment.
To read an assessment, select an issue below:
Immunization Status of Tennessee Counties
These infographics provide information about the immunization status of kindergarten students in each of Tennessee's 95 counties. High immunization coverage rates are critical if vaccine-preventable disease outbreaks are to be avoided.
To view an infographic, select a county below:
Tennessee Reports on Healthcare Associated Infections
Healthcare associated infections (HAI) are acquired by patients during the course of receiving treatment for other conditions within a healthcare setting. In Tennessee, hospitals and long-term acute care facilities are required to reporting certain HAIs to the Tennessee Department of Health through the Centers for Disease Control and Prevention's National Healthcare Safety Network.
To read Reports on Healthcare Associated Infections, select an issue below:
EPI-News is a newsletter which is published by CEDEP to inform the public health community, the private medical community, and the general public on issues related to occurrence of diseases and notifiable conditions within the state.
To be placed on the mailing list for this publication, call 800-404-3006 or e-mail. To read the newsletter online, select an issue below:
Acute Chemical Releases
Tennessee's National Toxic Substance Incidents Program (NTSIP) performs acute hazardous chemical exposure surveillance. Acute toxic incidents may range from illicit methamphetamine lab explosions in homes to chemical poisoning in automobiles and from industrial chemical releases to transportation incidents. These events frequently require actions to protect public health such as evacuation, in-place sheltering, or decontamination.
To read an Annual NTSIP Report, select a year below:
About Disease and Event Reporting in TN
Communicable diseases are easily spread from person to person. Prompt notification of a communicable disease can allow public health officials to locate and treat exposed persons, identify and contain outbreaks, and interrupt disease transmission. The information obtained from disease notification is also used to monitor disease trends, identify high risk groups, develop policy, and design prevention programs.
- More information on Reportable Diseases and Events
- More Information on Assigning MMWR Week in Tennessee
Finalized Data Published Annually
Finalized data on the number and distribution of diseases and events reported to CEDEP are published annually. Click on a link below to access finalized data available for 1995-2012.
- HIV/AIDS/STD Data Surveillance Reports
- All Other Reportable Diseases and Events New! Interactive Dashboard
Preliminary Data Published Weekly
Preliminary data on the number and distribution of diseases and events reported to CEDEP are published weekly. Preliminary data are only provided for years during which finalized data are not available. Click on a link below to access preliminary data published weekly during 2012 through 2014.


text:
Just because you have a small master bedroom or guest bedroom doesn't mean you can't create a stylish space to sleep and get away from it all! These 5 space-saving tips can help you design a bedroom that you'll love waking up to every morning!
1. Create a focal point.
Creating a single focal point for the bedroom can distract from the small size. An oversized headboard or large painting may seem counterintuitive, but these things can draw the gaze and pull the whole room together.
2. Use Neutral Colors
You can make a space feel more open and clean by using neutral colors on the largest items in a room, which in this case would be the wall and bed. White, beige, and gray are great options that can be accented with brightly colored pillows, throw blankets and accessories.
3. Center the Room Around Windows
Although many designers will say not to block windows (and therefore the view) with furniture, you may not have many options with a small bedroom. Instead, center the bed under windows and use this as the focal point for the room. Beautiful curtains can help frame both the window and the bed like a canopy.
4. Vertical Stripes
Incorporating vertical stripes with wallpaper, curtains or artwork can help draw the eye up the wall and create the illusion of more space. Hanging curtains high above the window frame can have the same effect.
5. Accent Wall
You can make a small room seem larger by creating a feeling of more depth by painting a dark accent wall. Combining a bright color (like the neutral tones listed above) with a darker accent color will create contrast and make the space more interesting.
Want to learn more about creating the perfect bedroom? Read more articles on our blog or browse a selection of our bedroom furniture.


text:
We believe that keeping personal information secure is one of our most important responsibilities. We completely restrict access to personal information about you, and will never transfer your personal information or email address to anyone or any company. We safeguard your personal information, according to established security standards and procedures, by maintaining physical, electronic, and procedural safeguards for the information.
Your personal information will never be sold or given to anyone or company. You will never receive any unsolicited email from transacting business with us. You have our promise and guarantee.


text:
Request for Comments: 7433
Category: Standards Track
J. Rafferty
Human Communications
January 2015
A Mechanism for Transporting User-to-User Call Control Information
in SIP
There is a class of applications that benefit from using SIP to exchange User-to-User Information (UUI) data during session establishment. This information, known as call control UUI data, is a small piece of data inserted by an application initiating the session and utilized by an application accepting the session. The syntax and semantics for the UUI data used by a specific application are defined by a UUI package. This UUI data is opaque to SIP and its function is unrelated to any basic SIP function. This document defines a new SIP header field, User-to-User, to transport UUI data, along with an extension mechanism.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7433.
Copyright Notice
Copyright © 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Requirements Discussion . . . . . . . . . . . . . . . . . . . 4 4. Normative Definition . . . . . . . . . . . . . . . . . . . . 5 4.1. Syntax for UUI Header Field . . . . . . . . . . . . . . . 6 4.2. Hex Encoding Definition . . . . . . . . . . . . . . . . . 7 4.3. Source Identity of UUI Data . . . . . . . . . . . . . . . 7 5. Guidelines for UUI Packages . . . . . . . . . . . . . . . . . 9 5.1. Extensibility . . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6.1. Registration of User-to-User Header Field . . . . . . . . 11 6.2. Registration of User-to-User Header Field Parameters . . 11 6.3. Registration of UUI Packages . . . . . . . . . . . . . . 11 6.4. Registration of UUI Content Parameters . . . . . . . . . 12 6.5. Registration of UUI Encoding Parameters . . . . . . . . . 12 6.6. Registration of SIP Option Tag . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . 15 Appendix A. Other Possible Mechanisms . . . . . . . . . . . . . 17 A.1. Why INFO is Not Used . . . . . . . . . . . . . . . . . . 17 A.2. Why Other Protocol Encapsulation UUI Mechanisms Are Not Used . . . . . . . . . . . . . . . . . . . . . . . . . . 17 A.3. MIME Body Approach . . . . . . . . . . . . . . . . . . . 17 A.4. URI Parameter . . . . . . . . . . . . . . . . . . . . . . 18 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Overview
This document describes the transport of UUI data using SIP [RFC3261]. It defines a mechanism for the transport of general application UUI data and for the transport of the call control related ITU-T Recommendation Q.931 User-user information element [Q931] and ITU-T Recommendation Q.763 User-to-User information parameter [Q763] data in SIP. UUI data is widely used in the Public Switched Telephone Network (PSTN) today for contact centers and call centers. There is also a trend for the related applications to transition from ISDN to SIP. The UUI extension for SIP may also be used for native SIP User Agents (UAs) implementing similar services and to interwork with ISDN services. Note that in most cases, there is an a priori understanding between the UAs in regard to what to do with received UUI data. This document enables the definition of packages and related attributes that can make such understandings more explicit.
The UUI mechanism is designed to meet the use cases, requirements, and call flows for SIP call control UUI detailed in [RFC6567]. All references to requirement numbers (REQ-N) and figure numbers refer to [RFC6567].
The mechanism is a new SIP header field, along with a new SIP option tag. The header field carries the UUI data, along with parameters indicating the encoding of the UUI data, the UUI package, and optionally the content of the UUI data. The package definition contains details about how a particular application can utilize the UUI mechanism. The header field can be included (sometimes called "escaped") into URIs supporting referral and redirection scenarios. In these scenarios, the History-Info header field is used to indicate the inserter of the UUI data. The SIP option tag can be used to indicate support for the header field. Support for the UUI header field indicates that a UA is able to extract the information in the UUI data and pass it up the protocol stack. Individual packages using the UUI mechanism can utilize SIP media feature tags to indicate that a UA supports a particular UUI package. Guidelines for defining UUI packages are provided.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
Note that the <allOneLine> tag convention from SIP Torture Test Messages [RFC4475] is used to show that there are no line breaks in the actual message syntax.
3. Requirements Discussion
This section describes how the User-to-User header field meets the requirements in [RFC6567]. The header field can be included in INVITE requests and responses and BYE requests and responses, meeting REQ-1 and REQ-2.
For redirection and referral use cases and REQ-3, the header field is included (escaped) within the Contact or Refer-To URI. The details of this mechanism as it applies for redirection and referral use cases are covered in Section 4.1.
Since SIP proxy forwarding and retargeting does not affect header fields, the header field meets REQ-4.
The UUI header field will carry the UUI data and not a pointer to the data, so REQ-5 is met.
Since the basic design of the UUI header field is similar to the ISDN UUI service, interworking with PSTN protocols is straightforward and is documented in a separate specification [RFC7434], meeting REQ-6.
Requirements REQ-7, REQ-8, and REQ-10 relate to discovery of the mechanism and supported packages, and hence applications. REQ-7 relates to support of the UUI header field, while REQ-8 relates to routing based on support of the UUI header field. REQ-7 is met by defining a new SIP option tag "uui". The use of a Require:uui in a request or Supported:uui in an OPTIONS response could be used to require or discover support of the mechanism. The presence of a Supported:uui or Require:uui header field can be used by proxies to route to an appropriate UA, meeting REQ-8. However, note that only UAs are expected to understand the UUI data -- proxies and other intermediaries do not. REQ-10 is met by utilizing SIP feature tags [RFC3840]. For example, the feature tag "sip.uui-isdn" could be used to indicate support of the ISDN UUI package, or "sip.uui-pk1" could be used to indicate support for a particular package, pk1.
Proxies commonly apply policy to the presence of certain SIP header fields in requests by either passing them or removing them from requests. REQ-9 is met by allowing proxies and other intermediaries to remove UUI header fields in a request or response based on policy.
Carrying UUI data elements of at least 129 octets is trivial in the UUI header field, meeting REQ-11. Note that avoiding having very large UUI data elements is a good idea, as SIP header fields have traditionally not been large.
To meet REQ-12 for the redirection and referral use cases, the History-Info header field [RFC7044] can be used. In these retargeting cases, the changed Request-URI will be recorded in the History-Info header field along with the identity of the element that performed the retargeting.
The requirement for integrity protection in REQ-13 could be met by the use of an S/MIME signature over a subset of header fields, as defined in "SIP Header Privacy and Integrity using S/MIME: Tunneling SIP", Section 23.4 of RFC 3261. Note that the lack of deployment of S/MIME with SIP means that, in general, REQ-13 is not met. The requirement of REQ-14 for end-to-end privacy could be met using S/MIME or using encryption at the application layer. Note that the use of S/MIME to secure the UUI data will result in an additional body being added to the request. Hop-wise Transport Layer Security (TLS) [RFC5246] allows the header field to meet REQ-15 for hop-by-hop security.
4. Normative Definition
This document defines a new SIP header field "User-to-User" to transport call control UUI data to meet the requirements in [RFC6567].
To help tag and identify the UUI data used with this header field, "purpose", "content", and "encoding" header field parameters are defined. The "purpose" header field parameter identifies the package that defines the generation and usage of the UUI data for a particular application. The value of the "purpose" parameter is the package name, as registered in the "UUI Packages" subregistry defined in Section 6.3. For the case of interworking with the ISDN UUI service, the ISDN UUI service interworking package is used. The default value for the "purpose" header field is "isdn-uui" as defined in [RFC7434]. If the "purpose" header field parameter is not present, the ISDN UUI MUST be used. The "content" header field parameter identifies the actual content of the UUI data. If not present, the default content defined for the package MUST be used. Newly defined UUI packages MUST define or reference at least a default "content" value. The "encoding" header field parameter indicates the method of encoding the information in the UUI data associated with a particular "content" value. This specification only defines "encoding=hex". If the "encoding" header field parameter is not present, the default encoding defined for the package MUST be used.
UUI data is considered an opaque series of octets. This mechanism MUST NOT be used to convey a URL or URI, since the Call-Info header field in [RFC3261] already supports this use case.
4.1. Syntax for UUI Header Field
The UUI header field can be present in INVITE requests and responses and in BYE requests and responses. Note that when the UUI header is used in responses, it can only be utilized in end-to-end responses, e.g., 1xx (excluding 100), 2xx, and 3xx responses.
The following syntax specification uses the Augmented Backus-Naur Form (ABNF) as described in RFC 5234 and extends RFC 3261 (where token, quoted-string, and generic-param are defined).
UUI = "User-to-User" HCOLON uui-value *(COMMA uui-value) uui-value = uui-data *(SEMI uui-param) uui-data = token / quoted-string uui-param = pkg-param / cont-param / enc-param / generic-param pkg-param = "purpose" EQUAL pkg-param-value pkg-param-value = token cont-param = "content" EQUAL cont-param-value cont-param-value = token enc-param = "encoding" EQUAL enc-param-value enc-param-value = token / "hex"
Each package defines how many User-to-User header fields of each package may be present in a request or a response. A sender MAY include multiple User-to-User header fields, and a receiver MUST be prepared to receive multiple User-to-User header fields. Consistent with the rules of SIP syntax, the syntax defined in this document allows any combination of individual User-to-User header fields or User-to-User header fields with multiple comma separated UUI data elements. Any size limitations on the UUI data for a particular purpose are to be defined by the related UUI package.
UAs SHALL ignore UUI data from packages or encoding that they do not understand.
For redirection use cases, the header field is included (escaped) within the Contact URI. For referral use cases, the header field is included (escaped) within the Refer-To URI. For example, if a UA supports this specification, it SHOULD include any UUI data included in a redirection URI (if the UUI data and encoding is understood).
Note that redirection can occur multiple times to a request. Currently, UAs that support attended transfer support the ability to include a Replaces header field [RFC3891] into a Refer-To URI, and when acting upon this URI, UAs add the Replaces header field to the triggered INVITE. This sort of logic and behavior is utilized for the UUI header field (that is, the UUI header field is included in the triggered INVITE). The UA processing the REFER [RFC3515] or the 3xx response to the INVITE SHOULD support the UUI mechanism. If the REFER or redirect target does not support UUI, the UUI header will be discarded as per [RFC3261]. However, this may limit the utility of use cases that depend upon the UUI being supported by all elements.
Here is an example of an included User-to-User header field from the redirection response F2 of Figure 2 in [RFC6567]:
<allOneLine> Contact: <sip:+email@example.com?User-to-User= 56a390f3d2b7310023a2%3Bencoding%3Dhex%3Bpurpose%3Dfoo%3B content%3Dbar> </allOneLine>
The resulting INVITE F4 would contain:
User-to-User: 56a390f3d2b7310023a2;encoding=hex;purpose=foo;content=bar
4.2. Hex Encoding Definition
This specification defines hex encoding of UUI data. When the value of "hex" is used in the "encoding" parameter of a header field, the data is encoded using base16 encoding according to Section 8 of [RFC4648]. The hex-encoded value is normally represented using the "token" construction from RFC 3261, although the "quoted-string" construction is permitted, in which case the quotes MUST be ignored.
If a canonicalized version of a normally case-insensitive hex encoded UUI data object is needed for a digital signature or integrity checking, then the base16 encoding with all upper case MUST be used.
4.3. Source Identity of UUI Data
It is important for the recipient of UUI data to know the identity of the UA that inserted the UUI data. In a request without a History- Info header field, the identity of the entity that inserted the UUI data will be assumed to be the source of the SIP message. For a SIP request, typically this is the UA identified by the URI in the From header field or a P-Asserted-Identity [RFC3325] header field. In a request with a History-Info header field, the recipient needs to parse the Targeted-to-URIs present (hi-targeted-to-uri defined in
[RFC7044]) to see if any included User-to-User header fields are present. If an included User-to-User header field is present and matches the UUI data in the request, this indicates that redirection has taken place, resulting in the inclusion of UUI data in the request. The inserter of the UUI data will be the UA identified by the Targeted-to-URI of the History-Info element prior to the element with the included UUI data. In a response, the inserter of the UUI data will be the identity of the UA that generated the response. Typically, this is the UA identified in the To header field of the response. Note that any updates to this identity by use of the SIP connected identity extension [RFC4916] or other identity modifiers will update this information.
For an example of History-Info and redirection, consider Figure 2 from [RFC6567] where the Originating UA is Carol, the Redirector Bob, and the Terminating UA Alice. The INVITE F4 containing UUI data could be:
INVITE sips:firstname.lastname@example.com SIP/2.0 Via: SIP/2.0/TLS lab.example.com:5061 ;branch=z9hG4bKnashds9 To: Bob <sips:email@example.com> From: Carol <sips:firstname.lastname@example.com>;tag=323sf33k2 Call-ID: dfaosidfoiwe83ifkdf Max-Forwards: 70 Contact: <sips:firstname.lastname@example.com> Supported: histinfo User-to-User: 342342ef34;encoding=hex History-Info: <sips:firstname.lastname@example.com>;index=1 <allOneLine> History-Info: <sips:email@example.com?Reason=SIP%3Bcause%3D302 &User-to-User=342342ef34%3Bencoding%3Dhex>;index=1.1;rc=1 </allOneLine>
Without the redirection captured in the History-Info header field, Alice would conclude that the UUI data was inserted by Carol. However, the History-Info containing UUI data (index=1.1) indicates that the inserter was Bob (index=1).
To enable maintaining a record of the inserter identity of UUI data, UAs supporting this mechanism SHOULD support History-Info [RFC7044] and include Supported: histinfo in all requests and responses.
If a border element such as a proxy or a Back-to-Back User Agent (B2BUA) removes a History-Info header field containing a User-to-User parameter, the UA consuming the UUI data may not be able at the SIP level to identify the source of the UUI data.
5. Guidelines for UUI Packages
UUI packages defined using this SIP UUI mechanism MUST follow the "Standards Action" guideline as defined in [RFC5226] and publish a Standards Track RFC that describes the usage. The CUSS WG chose to adopt this conservative policy while it considers other potential registration policies. Note that this mechanism is not suitable for the transport of arbitrary data between UAs. The following guidelines are provided to help determine if this mechanism is appropriate or not. The SIP UUI mechanism is applicable when all of the following conditions are met:
- The information is generated and consumed by an application during session setup using SIP, but the application is not necessarily SIP aware.
- The behavior of SIP entities that support it is not significantly changed (as discussed in Section 4 of [RFC5727]).
- UAs are the generators and consumers of the UUI data. Proxies and other intermediaries may route based on the presence of a User-to-User header field or a particular package tag but do not otherwise consume or generate the UUI data.
- There are no privacy issues associated with the information being transported (e.g., geolocation or emergency-related information are examples of inappropriate UUI data).
- The UUI data is not being utilized for User-to-User Remote Procedure Calls (RPCs).
UUI packages define the semantics for a particular application usage of UUI data. The content defines the syntax of the UUI data, while the encoding defines the encoding of the UUI data for the content. Each content is defined as a stream of octets, which allows multiple encodings of that content. For example, packages may define:
- The SIP methods and responses in which the UUI data may be present.
- The maximum number of UUI data elements that may be inserted into a request or response. The default is one per encoding. Note that a UA may still receive a request with more than this maximum number due to redirection. The package needs to define how to handle this situation.
- The default values for content and encoding if they are not present. If the same UUI data may be inserted multiple times with different encodings, the package needs to state this. A package may support and define multiple contents and their associated encodings and reuse contents defined by other packages.
- Any size limitations on the UUI data. Size needs to be specified in terms of the octet stream output of the content, since the size of the resulting uui-data element will vary depending on the encoding scheme.
A package MUST define a "purpose" header field value to identify the package in the coding. A package MUST describe the new application that is utilizing the UUI data and provide some use case examples. The default "content" value MUST be defined or referenced in another document for the package. Additional allowed contents MAY also be defined or referenced. Any restrictions on the size of the UUI data MUST be described. In addition, a package MAY define a media feature tag per [RFC3840] to indicate support for this UUI package. For example, the media feature tag "sip.uui-pk1" could be defined to indicate support for a UUI package named pk1. The definition of a new SIP option tag solely to identify support for a UUI package is NOT RECOMMENDED unless there are additional SIP behaviors needed to implement this feature.
For an example UUI package definition, see [RFC7434].
5.1. Extensibility
New "content" values MUST describe the semantics of the UUI data and valid encodings, and give some example use cases. A previously defined UUI content value can be used in a new package. In this case, the semantics and usage of the content by the new package is defined within the new package. New UUI content types cannot be added to existing packages -- instead, a new package would need to be defined. New content values that are defined are added to the IANA registry with a Standards Track RFC, which needs to discuss the issues in this section. If no new encoding value is defined for a content, the encoding defaults to "hex" as defined in this document. In this case, the "hex" value will be explicitly stated via the encoding parameter as the encoding for the content.
New "encoding" values associated with a new content MUST reference a specific encoding scheme (such as "hex", which is defined in this specification) or define the new encoding scheme. A previously defined UUI encoding value can be used with a newly defined content. In this case, the usage of the encoding is defined by the content definition. New UUI encodings cannot be added to existing contents -- instead, a new content would need to be defined. Newly defined encoding values are added to the IANA registry with a Standards Track RFC, which needs to discuss the issues in this section.
6. IANA Considerations
6.1. Registration of User-to-User Header Field
This document defines a new SIP header field named "User-to-User".
The following row has been added to the "Header Fields" section of the SIP parameter registry:
+------------------+--------------+-----------+ | Header Name | Compact Form | Reference | +------------------+--------------+-----------+ | User-to-User | | [RFC7433] | +------------------+--------------+-----------+
6.2. Registration of User-to-User Header Field Parameters
This document defines the parameters for the header field defined in the preceding section. The header field "User-to-User" can contain the parameters "encoding", "content", and "purpose".
The following rows have been added to the "Header Field Parameters and Parameter Values" section of the SIP parameter registry:
+------------------+----------------+-------------------+-----------+ | Header Field | Parameter Name | Predefined Values | Reference | +------------------+----------------+-------------------+-----------+ | User-to-User | encoding | Yes | [RFC7433] | +------------------+----------------+-------------------+-----------+ | User-to-User | content | No | [RFC7433] | +------------------+----------------+-------------------+-----------+ | User-to-User | purpose | No | [RFC7433] | +------------------+----------------+-------------------+-----------+
6.3. Registration of UUI Packages
This specification establishes the "UUI Packages" subregistry under <http://www.iana.org/assignments/sip-parameters>.
The descriptive text for this subregistry is:
UUI packages provide information about the usage of the UUI data in a User-to-User header field [RFC7433].
The registration policy for this registry is "Standards Action" as defined in [RFC5226].
+------------+------------------------------------------+-----------+ | Package | Description | Reference | +------------+------------------------------------------+-----------+
6.4. Registration of UUI Content Parameters
This specification establishes the "UUI Content Parameters" subregistry under <http://www.iana.org/assignments/sip-parameters>.
The descriptive text for this subregistry is:
UUI content provides information about the content of the UUI data in a User-to-User header field [RFC7433].
The registration policy for this registry is "Standards Action" as defined in [RFC5226].
+------------+------------------------------------------+-----------+ | Content | Description | Reference | +------------+------------------------------------------+-----------+
6.5. Registration of UUI Encoding Parameters
This specification establishes the "UUI Encoding Parameters" subregistry under <http://www.iana.org/assignments/sip-parameters> and initiates its population with the table below.
The descriptive text for this subregistry is:
UUI encoding provides information about the encoding of the UUI data in a User-to-User header field [RFC7433].
The registration policy for this registry is "Standards Action" as defined in [RFC5226].
+-----------+-------------------------------------------+-----------+ | Encoding | Description | Reference | +-----------+-------------------------------------------+-----------+ | hex | The UUI data is encoded using hexadecimal | [RFC7433] | +-----------+-------------------------------------------+-----------+
6.6. Registration of SIP Option Tag
This specification registers a new SIP option tag, as per the guidelines in Section 27.1 of [RFC3261].
This document defines the SIP option tag "uui".
The following row has been added to the "Option Tags" section of the SIP Parameter Registry:
+------------+------------------------------------------+-----------+ | Name | Description | Reference | +------------+------------------------------------------+-----------+ | uui | This option tag is used to indicate that | [RFC7433] | | | a UA supports and understands the | | | | User-to-User header field. | | +------------+------------------------------------------+-----------+
7. Security Considerations
UUI data can potentially carry sensitive information that might require confidentiality protection for privacy or integrity protection from third parties that may wish to read or modify the UUI data. The three security models described in [RFC6567] may be applicable for the UUI mechanism.
One model treats the SIP layer as untrusted and requires end-to-end integrity protection and/or encryption. This model can be achieved by providing these security services at a layer above SIP. In this case, applications are encouraged to use their own integrity and/or encryption mechanisms before passing it to the SIP layer.
The second approach is for the application to pass the UUI without any protection to the SIP layer and require the SIP layer to provide this security. This approach is possible in theory, although its practical use would be extremely limited. To preserve multi-hop or end-to-end confidentiality and integrity of UUI data, approaches using S/MIME or IPsec can be used, as discussed in the review of REQ-13 and REQ-14 in Section 3 of this document. However, the lack of deployment of these mechanisms means that applications cannot in general rely on them being present.
The third model utilizes a trust domain and relies on perimeter security at the SIP layer. This is the security model of the PSTN and ISDN where UUI is commonly used today. This approach uses hop- by-hop security mechanisms and relies on border elements for filtering and application of policy. Standard deployed SIP security mechanisms such as TLS transport offer privacy and integrity protection properties on a hop-by-hop basis at the SIP layer.
If the UUI data was included by the UA originator of the SIP request or response, normal SIP mechanisms can be used to determine the identity of the inserter of the UUI data. If the UUI data was included by a UA that was not the originator of the request, a History-Info header field can be used to determine the identity of the inserter of the UUI data. UAs can apply policy based on the origin of the UUI data using this information. In short, the UUI data included in an INVITE can be trusted as much as the INVITE itself can be trusted.
Note that it is possible that this mechanism could be used as a covert communication channel between UAs, conveying information unknown to the SIP network.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002, <http://www.rfc-editor.org/info/rfc3261>. [RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer Method", RFC 3515, April 2003, <http://www.rfc-editor.org/info/rfc3515>. [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)", RFC 3840, August 2004, <http://www.rfc-editor.org/info/rfc3840>. [RFC3891] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation Protocol (SIP) "Replaces" Header", RFC 3891, September 2004, <http://www.rfc-editor.org/info/rfc3891>. [RFC4474] Peterson, J. and C. Jennings, "Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)", RFC 4474, August 2006, <http://www.rfc-editor.org/info/rfc4474>. [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006, <http://www.rfc-editor.org/info/rfc4648>. [RFC4916] Elwell, J., "Connected Identity in the Session Initiation Protocol (SIP)", RFC 4916, June 2007, <http://www.rfc-editor.org/info/rfc4916>. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>. [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008, <http://www.rfc-editor.org/info/rfc5246>. [RFC7044] Barnes, M., Audet, F., Schubert, S., van Elburg, J., and C. Holmberg, "An Extension to the Session Initiation Protocol (SIP) for Request History Information", RFC 7044, February 2014, <http://www.rfc-editor.org/info/rfc7044>. [RFC7434] Drage, K. and A. Johnston, "Interworking ISDN Call Control User Information with SIP", RFC 7434, January 2015, <http://www.rfc-editor.org/info/rfc7434>.
8.2. Informative References
[Q1980] ITU-T, "The Narrowband Signalling Syntax (NSS) - Syntax Definition", ITU-T Recommendation Q.1980.1, <http://www.itu.int/itudoc/itu-t/aap/sg11aap/history/ q1980.1/q1980.1.html>. [Q763] ITU-T, "Signalling System No. 7 - ISDN User Part formats and codes", ITU-T Recommendation Q.763, <http://www.itu.int/rec/T-REC-Q.763-199912-I/en>. [Q931] ITU-T, "ISDN user-network interface layer 3 specification for basic call control", ITU-T Recommendation Q.931, <http://www.itu.int/rec/T-REC-Q.931-199805-I/en>. [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks", RFC 3325, November 2002, <http://www.rfc-editor.org/info/rfc3325>. [RFC3372] Vemuri, A. and J. Peterson, "Session Initiation Protocol for Telephones (SIP-T): Context and Architectures", BCP 63, RFC 3372, September 2002, <http://www.rfc-editor.org/info/rfc3372>. [RFC4475] Sparks, R., Hawrylyshen, A., Johnston, A., Rosenberg, J., and H. Schulzrinne, "Session Initiation Protocol (SIP) Torture Test Messages", RFC 4475, May 2006, <http://www.rfc-editor.org/info/rfc4475>. [RFC5727] Peterson, J., Jennings, C., and R. Sparks, "Change Process for the Session Initiation Protocol (SIP) and the Real- time Applications and Infrastructure Area", BCP 67, RFC 5727, March 2010, <http://www.rfc-editor.org/info/rfc5727>. [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session Initiation Protocol (SIP) INFO Method and Package Framework", RFC 6086, January 2011, <http://www.rfc-editor.org/info/rfc6086>. [RFC6567] Johnston, A. and L. Liess, "Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP", RFC 6567, April 2012, <http://www.rfc-editor.org/info/rfc6567>.
Appendix A. Other Possible Mechanisms
Two other possible mechanisms for transporting UUI data will be described: MIME body and URI parameter transport.
A.1. Why INFO is Not Used
Since the INFO method [RFC6086] was developed for ISDN User Part (ISUP) interworking of User-to-User Information, it might seem to be the logical choice here. For non-call control User-to-User Information, INFO can be utilized for end-to-end transport. However, for transport of call control User-to-User Information, INFO can not be used. As the call flows in [RFC6567] show, the information is related to an attempt to establish a session and needs to be passed with the session setup request (INVITE), responses to that INVITE, or session termination requests. As a result, it is not possible to use INFO in these cases.
A.2. Why Other Protocol Encapsulation UUI Mechanisms Are Not Used
Other protocols have the ability to transport UUI data. For example, consider the ITU-T Recommendation Q.931 User-user information element [Q931] and the ITU-T Recommendation Q.763 User-to-User information parameter [Q763]. In addition, the Narrowband Signalling System (NSS) [Q1980] is also able to transport UUI data. Should one of these protocols be in use, and present in both User Agents, then utilizing these other protocols to transport UUI data might be a logical solution. Essentially, this is just adding an additional layer in the protocol stack. In these cases, SIP is not transporting the UUI data; it is encapsulating another protocol, and that protocol is transporting the UUI data. Once a mechanism to transport that other protocol using SIP exists, the UUI data transport function is essentially obtained without any additional effort or work.
However, the CUSS working group believes, consistent with its charter, that SIP needs to have its own native UUI data transport mechanism. It is not reasonable for a SIP UA to have to implement another entire protocol (either ISDN or NSS, for example) just to get the very simple UUI data transport service. Of course, this work does not preclude anyone from using other protocols with SIP to transport UUI data.
A.3. MIME Body Approach
One method of transport is to use a MIME body. This is in keeping with the Session Initiation Protocol for Telephones (SIP-T) architecture [RFC3372] in which MIME bodies are used to transport ISUP information. Since the INVITE will normally have a Session
Description Protocol (SDP) message body, the resulting INVITE with SDP and UUI data will be multipart MIME. This is not ideal as many SIP UAs do not support multipart MIME INVITEs.
A bigger problem is the insertion of a UUI message body by a redirect server or in a REFER. The body would need to be encoded in the Contact URI of the 3xx response or the Refer-To URI of a REFER. Currently, the authors are not aware of any UAs that support this capability today for any body type. As such, the complete set of semantics for this operation would need to be determined and defined. Some issues will need to be resolved, such as, do all the Content-* header fields have to be included as well? And, what if the included Content-Length does not agree with the included body?
Since proxies cannot remove a body from a request or response, it is not clear how this mechanism could meet REQ-9.
The requirement for integrity protection could be met by the use of an S/MIME signature over the body, as defined in "Securing MIME bodies", Section 23.3 of RFC 3261. Alternatively, this could be achieved using [RFC4474]. The requirement for end-to-end privacy could be met using S/MIME encryption or using encryption at the application layer. However, note that neither S/MIME or RFC 4474 enjoys deployment in SIP today.
An example:
<allOneLine> Contact: <sip:+email@example.com?Content-Type= application/uui&body=ZeGl9i2icVqaNVailT6F5iJ90m6mvuTS4OK05M0vDk0Q4Xs> </allOneLine>
As such, the MIME body approach meets REQ-1, REQ-2, REQ-4, REQ-5, REQ-7, REQ-11, REQ-13, and REQ-14. Meeting REQ-12 seems possible, although the authors do not have a specific mechanism to propose. Meeting REQ-3 is problematic but not impossible for this mechanism. However, this mechanism does not seem to be able to meet REQ-9.
A.4. URI Parameter
Another proposed approach is to encode the UUI data as a URI parameter. This UUI parameter could be included in a Request-URI or in the Contact URI or Refer-To URI. It is not clear how it could be transported in a response that does not have a Request-URI, or in BYE requests or responses.
<allOneLine> Contact: <sip:+firstname.lastname@example.com;uui=ZeGl9i2icVqaNVailT 6F5iJ90m6mvuTS4OK05M0vDk0Q4Xs> </allOneLine>
An INVITE sent to this Contact URI would contain UUI data in the Request-URI of the INVITE. The URI parameter has a drawback in that a URI parameter carried in a Request-URI will not survive retargeting by a proxy as shown in Figure 2 of [RFC6567]. That is, if the URI is included with an Address of Record instead of a Contact URI, the URI parameter in the Request-URI will not be copied over to the Contact URI, resulting in the loss of the information. Note that if this same URI was present in a Refer-To header field, the same loss of information would occur.
The URI parameter approach would meet REQ-3, REQ-5, REQ-7, REQ-9, and REQ-11. It is possible the approach could meet REQ-12 and REQ-13. The mechanism does not appear to meet REQ-1, REQ-2, REQ-4, and REQ-14.
Joanne McMillen was a major contributor and coauthor of earlier versions of this document. Thanks to Paul Kyzivat for his contribution of hex encoding rules. Thanks to Spencer Dawkins, Keith Drage, Vijay Gurbani, and Laura Liess for their review of the document. The authors wish to thank Roland Jesske, Celine Serrut- Valette, Francois Audet, Denis Alexeitsev, Paul Kyzivat, Cullen Jennings, and Mahalingam Mani for their comments. Thanks to Scott Kelly and Joel Halpern for their reviews.
Authors' Addresses
Alan Johnston Avaya St. Louis, MO 63124 United States EMail: email@example.com James Rafferty Human Communications Norfolk, MA 02056 United States


text:
Lincoln at Peoria: The Turning Point explains how Lincoln�s speech at Peoria on October 16, 1854 was the turning point in the development of his antislavery campaign and his political career and thought. Here, Lincoln detailed his opposition to slavery�s extension and his determination to defend America�s Founding document from those who denied that the Declaration of Independence applied to black Americans.
Students of Abraham Lincoln know the canon of his major speeches — from his Lyceum Speech of 1838 to his "Final Remarks" delivered from a White House window, days before he was murdered in 1865. Less well-known are the two extraordinary speeches given at Springfield and Peoria two weeks apart in 1854. They marked Mr. Lincoln�s reentry into the politics of Illinois and, as he could not know, his preparation for the Presidency in 1861. These Lincoln addresses catapulted him into the debates over slavery which dominated Illinois and national politics for the rest of the decade. Lincoln delivered the substance of these arguments several times — certainly in Springfield on October 4, 1854, for which there are only press reports. A longer version came twelve days later in Peoria. To understand President Abraham Lincoln, one must understand the Peoria speech of October 16, 1854. It forms the foundation of his politics and principles, in the 1850s and in his Presidency.


text:
Brew Hop will help you select or customize a tour for your party led by local beer experts eager to share their passion for San Diego's craft beer.
Brew Hop features top local breweries like Stone, The Lost Abbey, Port Brewing, Ballast Point, Alesmith, Green Flash and dozens more.
Brew Hop guests are transported in comfort and style… and you can keep the party going by purchasing your favorite brews for the road!


text:
Princeton University graduate students Richard Baliban, William Cavendish, William Deringer and Andrew Huddleston have been named as co-winners of the Porter Ogden Jacobus Fellowship, Princeton's top honor for graduate students. The fellowship supports the final year of study and is awarded to students whose work has exhibited the highest scholarly excellence.
The Jacobus Fellows will be honored at Alumni Day ceremonies Saturday, Feb. 25, at Jadwin Gymnasium.
Baliban, a doctoral student in the Department of Chemical and Biological Engineering, earned a bachelor's degree in chemical engineering and mathematics from the University of Pennsylvania. Before enrolling at Princeton, Baliban worked as an engineer for ExxonMobil.
His dissertation focuses on the development of computational tools to identify and quantify peptides and proteins, with the goal of enhancing the accuracy of cell analysis. The technique is commonly used to analyze the root causes of breast cancer, gingivitis and other diseases. In addition, Baliban has worked on developing new frameworks for hybrid energy systems.
"Rich is without doubt a brilliant researcher with a great future lying ahead," said Baliban's dissertation adviser Christodoulos Floudas, the Stephen C. Macaleer '63 Professor in Engineering and Applied Science, and professor of chemical and biological engineering. "Primary characteristics of Rich are his amazing theoretical and computational ability, his impressive and smooth transition and interplay between theory and experiments, his natural scientific maturity and persistence when attacking challenging problems, his highly inquisitive and independent research mind, and his drive for perfection."
Baliban said he hopes to have a career involving alternative energy research in which he can contribute to a stronger national energy outlook by working on state-of-the-art research projects.
"I want to apply my engineering skills to industrial problems and develop solutions that are practical, effective and financially reasonable," he said.
Cavendish, a Ph.D. candidate in the Department of Mathematics, came to Princeton after studying mathematics as an undergraduate at the University of Chicago and as a master's student at Brown University.
Cavendish's studies focus on low-dimensional topology and geometry, two active areas of modern mathematics. His work addresses questions about symmetries of low-dimensional objects, such as the patterns in a chain-link fence.
"Though symmetry is most often thought of as a geometric phenomenon, symmetry is central to every field of mathematics from abstract algebra and number theory to differential equations and dynamics," Cavendish said.
His thesis adviser, David Gabai, said Cavendish is an enthusiastic student.
"He is very independent, he found his research problems and direction by himself, he absorbs mathematics voraciously, and fearlessly attacks problems that stump the most famous mathematicians. He learns difficult new techniques when needed and has taught me a lot more than I have taught him," said Gabai, the Hughes-Rogers Professor of Mathematics.
Deringer, a doctoral student in the history of science program, earned his bachelor's degree in history from Harvard University and a master's degree in the history of science from Princeton in 2009.
Deringer's dissertation builds on his master's studies, exploring the economic history of Britain's "financial revolution" from 1688 to 1738. His work has been informed by his professional experience as an investment-banking analyst.
"For my dissertation, I decided to investigate how mathematics, politics and ethics entwined in the economic controversies of early modern Britain," Deringer said. "I am committed to making that project one that transcends the traditionally large gaps between three historical subfields — the history of science, British political history and economic history — and also one that contributes to conversations in political science, sociology and economics."
His adviser, Professor of History Michael Gordin, noted that Deringer's scholarship "accomplishes two rare features for an early modern history of science dissertation: it is strikingly original, and it is very relevant."
Gordin added that Deringer is a "highly gifted historian" as well as a "fantastic teacher."
Huddleston, a Ph.D. candidate in the Department of Philosophy, studied as an undergraduate at Brown University and the University of Cambridge. He joined Princeton's graduate program in 2007.
Huddleston's dissertation examines the works of 19th-century German philosopher Friedrich Nietzsche, using Nietzsche's profound concern with the decadence and flourishing of cultures as a guiding thread for investigating the central themes in his ethics and social philosophy.
"I am eager to work out Nietzsche's philosophical positions not so much because I think he is obviously right about all of them, but because I think that what he does have to say is stimulating and provocative, even if it is sometimes overstated, and on occasion, shocking and repellent as well. So often the value of the history of philosophy is to remind us that we cannot always take our own views for granted," Huddleston said.
His adviser Alexander Nehamas, the Edmund N. Carpenter II Class of 1943 Professor in the Humanities and professor of philosophy and comparative literature, called Huddleston "the most promising young philosopher with an interest in Nietzsche and the philosophy of art in this country."