Department Name Foundation, Corporate & Government Relations: Fill & Download for Free

Thank you for your question. First, this response will provide a brief synopsis of the benefits and drawbacks that come with forming an LLC, S-Corporation, and C-Corporation. Second, this response will provide rough guidelines on how to form an LLC in Delaware.Limited Liability Company (LLC) form permits you to shield personal assets from business liability, requires you and your fellow owners to maintain separate business and personal account records, can be formed in all fifty states and the District of Columbia, provides you with a highly flexible management structure, has flexible tax reporting options, and are usually preferred by outside investors.An LLC will be ideal if your startup company anticipates losses for at least two years and you want to be able to pass the losses through to yourself and the other owners, you want a flexible choice of accounting methods, or your business will own real estate.S-Corporation and C-Corporation refers to your firm’s tax status. An S Corporation is considered a pass-through entity, which means the business itself isn't taxed. Instead, income is reported on the owners' personal tax returns. S Corporations are ideal for firms that want to minimize Social Security and Medicare salary taxes, use cash accounting methods, and lower IRS audit risk.Businesses taxed as C corporations are not pass through entities, cannot have more than 100 shareholders, and can only be held by U.S citizens. Income is taxed at the corporate level, and, if dividends are distributed, income is also taxed at the individual level as well. C Corporations provide their shareholders with limited liability and are ideal for firms that want to obtain venture capital financing, have flexible profit sharing rules, want to retain earnings, minimize social security and Medicare salary taxes, provide substantial fringe benefits to employees, own real estate, or lower IRS audit risk.If you want to form a Delaware LLC all you need to do is:(1) Come up with an LLC name. Under Delaware law, an LLC name must contain the words "Limited Liability Company" or the abbreviation "L.L.C." or "LLC." In addition, the name can contain the names of members, or the words "Club," "Foundation," "Fund," "Institute," "Society," "Union," "Syndicate," or "Trust." Your LLC’s name must not be deceptively like the names of other business entities already on file with the Delaware Secretary of State. Names may be checked for availability by searching the Department of State: Division of Corporations business name database. You can also reserve a name for a fee.(2) Appoint a Registered Agent.(3) File a certificate of formation that includes the LLC's name and the name and address of the LLC’s registered agent. The filing fee is $90.(4) Pay an annual $300 alternative entity tax and obtain an IRS Employer Identification Number. Unlike many states, Delaware does not have annual filing requirements for LLCs.Need assistance registering your corporation in Delaware? The corporate attorneys at LawTrades can walk you through the process at an affordable flat rate. Message me for more details.

Normally Quora for wealthy people are consultancy companies, legal departments and private clubs. But here are some of the concerns.Should I lobby for x law/policy ? Will it affect my stocks?I just bought a small company that complements the main corporate. Should I merge them or benefit from the speed of the small company?I offered to buy out x company. They asked for a ridiculous amount that is not feasible for us to pay. Should I release our version and compete directly with them until their prices drop?I want to delegate responsibilities to a CEO but I am not sure how to trust them with my baby and vision. Any hints?What are the downsides of billionaires converting their wealth into charity trusts? I know the upside of minimizing the taxes, but what are the risks?The president called me and gave me a ridiculous request to hire more people to speed up automation. How should I take advantage of this and did you get the same dumb request?Who is interested in the new space industry? Shall we create a new fund for it?I’m worried about the future of our name. My kids are too stupid and spoiled to take over the family business. What do you recommend?If I donated to x foundation, is there a risk to our brand or shall I donate anonymously?There is a new tax coming that will force us to lay off people. What should we do?

Funny thing that. Let me lead with an update from my old colleague Paul Vixie. He posted this to his LinkedIn feed earlier today.Paul is a respected name in the DNS space, running the F-root and the ISC which supports bind (one of the leading DNS implementations). But he’s clearly not on board with this. What gives?Let’s think a bit about how DNS works. Super simplified version here, be warned. When you want to access a computer by name versus IP address explicitly, you invoke your local resolver. Which when given a domain name, will attempt to create a fully qualified domain name if it’s not already, or if it is, attempt to resolve it - to turn the name into an IP address. The resolver maintains a local cache of names it’s already looked up - in addition to this cache potentially running an LRU algorithm to conserve space, it is bound by the rules of DNS to expire entries which have hit their time-to-live. So the name might or might not be there.If you don’t have a local hit, you pass it up-line to another resolver. That applies recursively - the rule is that if you send it to a smart resolver, if the data is not in its cache, it’s supposed to send to the Start of Authority for the domain. But if that SOA record is not in the cache, you send to the SOA for the TLD - so for “splorg.com” you would send to the SOA for “.com”. And if you didn’t have that in your cache, you’d send to the “root servers” who could help you out with the top level SOAs.Back in the day, when Mockapetris architected all this, links were slow and memory expensive. It was pretty common for - in the interests of preserving bandwidth - the TTLs to be pretty long (because stuff didn’t change hardly ever) and for each organization to run a local DNS hub, to which all campus connected computers would point.The cache could wind up being deep - the DNS implementation that I wrote for DEC’s VMS operating system effectively had unlimited cache, as I kept a working set of A records in physical memory and had a fast database in virtual memory for everything else. But sooner or later you had to kick requests up-line. It was pretty common to hit the first level resolvers on a frequent basis, the root resolvers almost never.This all worked because you were doing this to resolve stuff that didn’t change much - email servers, remote systems you’d log into or copy files to/from. And then the World Wide Web happened….Chaos pretty much ensued. Domain proliferation happened, and as browsers became more sophisticated, requests were run in parallel versus serialized, and as content proliferation also happened, a “simple web page” might be pulling assets from over 50 discrete sources. The number of DNS queries that your local computer was doing increased asymptotically, and the impact of queries taking too long became more significant.To combat that (and this is circa 2000-ish), Internet service providers started running their own very deep cache DNS resolvers. And your cable modem which provided network translation service, and ran DHCP for your home LAN, would “prefer” the DNS resolvers of the ISP, over pointing at root.This meant two things: first, they got to aggregate a lot of DNS requests, meaning that odds were really good that you wouldn’t have a cache miss. Second, if they wanted to, they could know a whole bunch about what you were doing with your computer. Without even bothering to snoop your actual traffic, the fact that they could see all of your DNS queries meant that they knew you looked at Powerball results on Saturday morning, went to “Nuns and Nazis” every evening about 11pm, and visited “Susie’s Sweet Scent Candles” every 2nd and 16th.That’s… potentially awkward. But not lethal. Unless your ISP happens to be the government and you happen to be in a repressive regime. In which case going to the How To Freedom website or hitting the how to apply for asylum pages at the US State Department might prove injurious to your health.To stop “corporate snooping” and institutional reigns of terror, Google, Cloudflare, OpenDNS and a few other organizations set up free and open DNS servers (starting circa 2006-ish). You can manually set your DNS to 8.8.8.8 or 1.1.1.1 or 208.67.222.222 or whatever and know that your DNS queries won’t be seen and cached by a more local DNS server.All of which is well and good, but…. well… you know… the operator can still SEE the packets. Even if its not running the intermediate DNS. So.. how do I fix that?That’s what DoH solves for. You run DNS over an HTTPS tunnel to an endpoint, and thence it’s unpacked and routed to the designated DNS server. So now, no one can either scope out your DNS queries at the resolver, or sniff the wire and see your DNS packets. Until you get to the DNS resolver.Sounds great, right?OK… sure. Except.What if you want control over your corporate network? What if you really want to know what your employees are actually doing? Because….well… reasons. Might be incipient paranoia. Might be a last vestige of being a server hugger. Might be valid, as in “you’re not supposed to be accessing a whole bunch of restricted sites from work on a work computer”.Or what if you’re a parent, and have been running a DNS proxy as part of your parental controls software?In any event, if you’re running DoH your internal network monitoring software has no clue what’s going on. Looks like any other encrypted HTTPS stream, completely opaque. You can tell that it’s SOMETHING, but not what. (Note: VPNs pose the same issue)So in late October, the Mozilla Foundation, which supports the Firefox browser and is terrifically more aggressive about promoting privacy, decided to enable DoH by default. Firefox DNS-over-HTTPS.You can turn it off. But by default, it’s opt-out. Also in their policies: they don’t allow Cloudflare in particular (and “others”) to accumulate personally identifying information. In theory, aggregated traffic is less susceptible to that sort of identification than directly connecting to a DNS resolver, but it can still happen.BTW, you can also enable this in Chrome. But it’s not a default.In addition to just flipping a bunch of people out that they did this, there’s a whole deeper layer: who, exactly, does the deeper resolving, and what do they know about you?Note that the Google and Cloudflare DNS services are fully monetized - these people use your information to make money off of knowing what you’re doing. Commercially, they’re a lot less likely to give a shit about it (but that “Nuns and Nazis” thing might get you pop up ads from “Nurses and Narwhals”). But there’s still a big matter of “someone, somewhere, has to be able to map this result to this requestor, and that knowledge is potentially power”.So who gets to know? And who decides?That’s one of the reasons that corporate users want to rope it all back into a server they control. And why DoH is potentially a problem.For users out there in userland, just doing your thing, not with a corporate computer, not on a corporate network, (and not a kid on a parentally monitored network), DoH looks like a pretty massive win.For security minded users with a touch more paranoia, you’ll want more control over where your DNS is unpacked, and you probably are using a VPN anyway. But you’re adept enough to reconfigure to suit.For corporate users, if you’re up to no good this is a win.For corporate admins, if you’re trying to find people up to no good, this is a nightmare.And for all the parties trying to figure out how to capture, aggregate and monetize your browsing habits? The middle men, the ISPs, they’re out of luck. The other guys? Could wind up being an interesting time - the battle is far from over.