Re: Use Case: Transaction Identification (travel use cases)

I think this use case is very real and touches the core of self-sovereign
identity. One thing that's not clear to me yet, though, is how can DIDs/VCs
actually avoid the risks of improper personal information management once
credentials and personal data have been shared with a relying party... Any
opinions shared by the community on this regard?

On Thu, Jul 5, 2018 at 1:15 AM, heather vescent <heathervescent@gmail.com>
wrote:

> Hi All,
>
> This is a little short and sweet use for transaction/travel
> identification. I'm unclear if this is a good use of DIDs or there may be
> technology built to better solve this. Also, to fully solve this problem,
> you'd need to have a solution that includes the verification of the
> identification (DID) from a lot of small businesses.
>
> It has been added to the DID use case document: https://docs.google.
> com/document/d/1wz8sakevXzO2OSMP341w7M2LjAMZfEQaTQEm_AOs3_Q/edit?usp=
> sharing
>
> Again, this is a draft concept and can be fleshed out more. I look forward
> to your comments and questions.
>
> -Heather
>
> ---
>
>
>
>
>
>
>
>
>
>
>
> *Name: Transaction Identification (e.g. travel use cases)Background:When
> traveling, hotels and other businesses need identification information.
> This is exacerbated when using new travel sites like AirBnB.Description:The
> problem: requirement to share personal information with hotels. Their data
> security is not secure. If one uses a stage name while traveling, you’ll
> need to reconcile that with financial information that has a legal name.
> With AirBnbs and other alternative hotels, individual hosts may want a copy
> of the driver’s license of not just the renter, but all guests (hotels
> often ask for this). But what are the security practices of these
> individuals? How can you confirm/share identity information to the
> satisfaction of the host/business owner and security PII of the user at the
> same time? Whether the PII is collected in a computer database or on slips
> of paper, there may be poor security practices. It is not the business of
> the hotel to secure data, it is their business to provide overnight
> accommodations. Thomas is a superhost in Joshua Tree and runs 3 AirBnBs.
> Even though AirBnB validates the guests identification before a
> reservation, Thomas always asks for a copy of their drivers license, which
> he stores as a photograph in his person cloud.Angela is traveling for two
> weeks on a roadtrip. Each night is at a different motel. Each motel asks
> for identification information when registering for the room. Angela is
> concerned with the security practices of the PII collected by these motels.
>  Sticky Wicket: Identity information is needed for transactions, but the
> people who collect and use this information have poor security practices -
> thus creating risk for the collected data. These systems may be low hanging
> fruit targets for hackers.Distinctive: Not sure if this is a good
> application of DIDs. It might be a heavy weight solution to this problem.
> There may be a better solution in conjunction with a specific payment
> mechanism (credit cards).Potential adjacent use cases - Where to use
> identity when traveling?- Stage names- Dead Name Club- In conjunction with
> a travel AI/agent- Real estate wire transfer details- Buying property,
> closing deals. Hacker has successfully phished a real estate agent, but
> wait quietly until a wire transfer message is sent to one of their buyers.
> After the legit real estate agent has sent the wire instructions, the
> hacker emails the buyers with *updated* wire instructions from the phished
> email account. The updated wire instructions go to the hacker’s bank
> account. *
>
> --
> Heather Vescent <http://www.heathervescent.com/>
> The Purple Tornado, Inc
> ~ The Future in Present Tense ~
>
> @heathervescent <https://twitter.com/heathervescent> | Film Futures
> <https://vimeo.com/heathervescent> | Medium
> <https://medium.com/@heathervescent/> | LinkedIn
> <https://www.linkedin.com/in/heathervescent/> | Future of Security Updates
> <https://app.convertkit.com/landing_pages/325779/>
>