RFC 3160:The Tao of IETF - A Novice's Guide to the...
RFC-Ref

company


Click on the red underlined text to get to the source

... express their opinions about issues affecting the Internet. However, it is not a place for companies or individuals to solicit or advertise, as noted in "IETF Discussion ...


... entirely due to the Olympian efforts of the local hosts, and their ability to beg, borrow and steal. The people and companies who donate their equipment, services and time are to be heartily ...
... Working Group lists, they will get a sense of whether or not their presence would be worthwhile for your company or for the Working Groups. ...
... Internet hardware or software, and no one from your company has ever attended an IETF meeting, it behooves you to come to a meeting if for no other ...
... This is not to say that companies should close up shop during IETF meeting weeks so everyone can go to the meeting. Marketing folks, ...
... even technical marketing folks, are usually safe in staying away from the IETF as long as some of the technical people from the company are at the meeting. Similarly, it isn't required, or likely useful, for everyone from a technical department to go, particularly if they are ...
... Working Group mailing lists. Many companies have just a few designated meeting attendees who are chosen for their ability to do complete and useful trip reports. ...
... vendors to try to sell their wares. People can certainly answer questions about their company and its products, but bear in mind that the IETF is not a trade show. This does not preclude people from ...


... probably come with a few slides prepared. Projectors for laptop- based presentations are available in all the meeting rooms. And here's a tip for your slides: don't put your company's logo on every one, even though it's common practice outside the IETF. The IETF ...
... don't even put their logo on their opening slide. The IETF is about technical content, not company boosterism. ...


... programs that interoperate. They don't exist to document the (possibly wonderful) ideas of their authors, nor do they exist so that a company can say "we have an IETF standard." If a standards- track RFC only has one implementation (whereas two are required for ...
... security patents, and the security community has responded very favorably to IBM for this (whereas a number of other companies have made themselves pariahs for their intractability on their security ...


... expertise. Do this for the benefit of the Internet community, not to get your name (or, even worse, your company's name) on a document. Draft authors are subject to all kinds of technical (and sometimes ...
... What Your Company Can Do ...
... with the open standards of the IETF, and tell the companies you buy from that you are doing so. Open Up -- If your company ...
... companies you buy from that you are doing so. Open Up -- If your company controls a patent that is used in an IETF standard, convince them to make the patent ...
... the standard. In the past few years, patents have caused a lot of serious problems for Internet standards because they prevent some companies from being able to freely implement the standards. Fortunately, many companies ...
... companies from being able to freely implement the standards. Fortunately, many companies have generously offered unlimited licenses for particular patents in order to help the IETF standards ...
... unlimited licenses for particular patents in order to help the IETF standards flourish. These companies are usually rewarded with positive publicity for the fact that they are not as greedy or short-sighted as other ...
... Join -- Become a member of ISOC. More importantly, urge any company that has benefited from the Internet to become a corporate member of ISOC ...


... that happened was that an Informational RFC was published. In both cases, the press is not fully to blame for the problem, since they are usually alerted to the story by a company trying to get publicity for a protocol that they developed or at least support. Of course, a bit ...



Google
Web
RFC-Ref