To Be Completed By Lru: Fill & Download for Free

Light Combat Aircraft Tejas or simply as we know LCA Tejas is the second in line indigenously produced fighter aircraft by Hindustan Aeronautics Limited after the HAL Marut.How Indigenous is LCA-Tejas has been the focus of discussion in India since the time it took its first flight in 2001. Over the years slowly but steadily efforts have been made to diversify the local supply chain and also replace foreign imported subsystems and components with locally manufactured ones and according to the Defence ministry at present indigenous content of the LCA-Tejas presently stands at 75.5% by numbers and 59.7% by Value of the aircraft.Now whenever we mark any aircraft about its component and its value, we term it by two;By ValueBy Line Replaceable Units/LRUsLower Line Replaceable Units/LLRUSo LCA Tejas is59.7% indigenous by ValueAnd 75.5% bu LRU and LLRUsNow what is Line Replaceable Units. These are the essential support item which is removed and replaced at the field level to restore the end item to an operational ready condition. For better understanding let us take the example of the AC-130 Gunship.Now as I said Line Replaceable Units and Lower Line Replaceable Units are the second things which needs to be accounted. So in LCA Tejas there are in total 344 LRUs/LLRUs involved.Out of which 210 LRUs/LLRUs are manufactured by our own country in the different PSUs, institutes and factories.And the rest 134 LRU/LLRUs are manufactured by foreign suppliers and are being imported. Out of which 42 units will be soon produced by India itself.The fly-by-wire system in Tejas is developed by Bharat Electronics Ltd. But there are critics who point out that engine is from US and radar at the moment is from Israel. However, the airforce in a way believes that nobody makes all the technology as these are open-source technology which includes radar, Egyptian pilot seats which can be purchased from anywhere.Reinventing the wheel and getting every component and sub component of a combat aircraft indigenously produced is not feasible. The reason is that these are low cost items and to set up a production line for a limited demand is not practical. Also, the requirement for multimode radar is in progress. Tejas uses Elta radar but, there are plans of replacing them in FOC aircraft or MK1A.In terms of weapons in aircraft at the moment is fine except the BVR missile and the MK1A is being fitted with the AESA radar which is top of the shack multimode radar in the airborne mode.Indian Components:Airframe and compositesLanding gearElectronic warfare suiteDisplaysFlight control system (Fly by wire system)crash resistant self sealing fuel tanks.valves, wires and plumbing.Joint development or custom imported components: These are components that are developed by sub-contracting to overseas development but are specific to LCA.Radar: This is in joint development with Elta but a custom Radar for LCA as per Indian requirementsTargeting podsLRUs: These are the brains of the aircraft and are quasi Indian. They use imported silicon Chips (we don't have semiconductor capability). However, the actual circuit board, system design, standards for interface and the software are 100% Indian.Missiles: Some are licence produced and others are fully Indian. Its a mix.Fully imported:Radar covering cone i.e the front cone section of the aircraft which is a quartz-based structure imported from the UK.Engine from the USAEjection seatssilicon semiconductor ICSInitially, the propulsion system or the engine chosen was GTRE GTX-35VS Kaveri developed by GTRE under DRDO.A little bit history about the Kaveri engine:The GTRE GTX-35VS Kaveri is a turbofan project developed by the (GTRE), a lab under the DRDOT the Kaveri was originally intended to power production models of the Tejas LCA fighter.This was approx 202 mn $ project.Later on the project was divided into two category: K9 and K 10K9: Will be completely indigenous with only foreign consultation and certification.K10: Will be a joint venture with a foreign partner.Problems that occurred:Kaveri engine in its present form uses directionally solidified blade technology which is rather an old tech and it couldn’t tolerate the high temperature in its combustion chamber called “Kabini”. The solution was “single crystal blades” The thrust generated was nearly 65 to 70% of what was needed. Performance decay at high altitude. A peculiar noise when in after burning mode..

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.

Light Combat Aircraft Tejas or simply as we know LCA Tejas is the second in line indigenously produced fighter aircraft by Hindustan Aeronautics Limited after the HAL Marut.How Indigenous is LCA-Tejas has been the focus of discussion in India since the time it took its first flight in 2001. Over the years slowly but steadily efforts have been made to diversify the local supply chain and also replace foreign imported subsystems and components with locally manufactured ones and according to the Defence ministry at present indigenous content of the LCA-Tejas presently stands at 75.5% by numbers and 59.7% by Value of the aircraft.Now whenever we mark any aircraft about its component and its value, we term it by two;By ValueBy Line Replaceable Units/LRUsLower Line Replaceable Units/LLRUSo LCA Tejas is 59.7% indigenous by ValueAnd 75.5% bu LRU and LLRUsNow, what are Line Replaceable Units? These are the essential support item which is removed and replaced at the field level to restore the end item to an operational ready condition. For better understanding let us take the example of the AC-130 Gunship.Now as I said Line Replaceable Units and Lower Line Replaceable Units are the second things which need to be accounted. So in LCA Tejas, there are in total 344 LRUs/LLRUs involved.Out of which 210 LRUs/LLRUs are manufactured by our own country in the different PSUs, institutes and factories.And the rest 134 LRU/LLRUs are manufactured by foreign suppliers and are being imported. Out of which 42 units will be soon produced by India itself.The fly-by-wire system in Tejas is developed by Bharat Electronics Ltd. But there are critics who point out that the engine is from US and radar at the moment is from Israel. However, the airforce in a way believes that nobody makes all the technology as these are open-source technology which includes radar, Egyptian pilot seats which can be purchased from anywhere.Reinventing the wheel and getting every component and sub-component of a combat aircraft indigenously produced is not feasible. The reason is that these are low-cost items and to set up a production line for a limited demand is not practical. Also, the requirement for multimode radar is in progress. Tejas uses Elta radar but, there are plans of replacing them in FOC aircraft or MK1A.In terms of weapons in aircraft at the moment is fine except the BVR missile and the MK1A is being fitted with the AESA radar which is top of the shack multimode radar in the airborne mode.Indian Components:Airframe and compositesLanding gearElectronic warfare suiteDisplaysFlight control system (Fly by wire system)crash-resistant self-sealing fuel tanks.valves, wires and plumbing.Joint development or custom imported components: These are components that are developed by sub-contracting to overseas development but are specific to LCA.Radar: This is in joint development with Elta but a custom Radar for LCA as per Indian requirementsTargeting podsLRUs: These are the brains of the aircraft and are quasi Indian. They use imported silicon Chips (we don't have semiconductor capability). However, the actual circuit board, system design, standards for interface and the software are 100% Indian.Missiles: Some are licence produced and others are fully Indian. Its a mix.Fully imported:Radar covering cone i.e the front cone section of the aircraft which is a quartz-based structure imported from the UK.Engine from the USAEjection seatssilicon semiconductor ICSInitially the propulsion system or the engine chosen was GTRE GTX-35VS Kaveri developed by GTRE under DRDO.A little bit history about the kaveri engine:The GTRE GTX-35VS Kaveri is a turbofan project developed by the (GTRE), a lab under the DRDOT the Kaveri was originally intended to power production models of the Tejas LCA fighter.This was approx 202 mn $ project.Later on, the project was divided into two categories: K9 and K 10K9: Will be completely indigenous with only foreign consultation and certification.K10: Will be a joint venture with a foreign partner.Problems that occured:Kaveri engine in its present form uses directionally solidified blade technology which is rather an old tech and it couldn’t tolerate the high temperature in its combustion chamber called “Kabini”. The solution was “single crystal blades” The thrust generated was nearly 65 to 70% of what was needed.Performance decay at high altitude.A peculiar noise when in after burning mode.If this had worked the ratio or percentage of indigenous products with Tejas would have been much more.There is no doubt that HAL Tejas is indigenous but sometimes it is also referred to as the world’s or Earth’s first LCA as it can load weapon’s of almost every country and is suitable for every country in the world.And yes we will use Uttam aesa band radar and in the future also we can use Kaveri engine then it will have more indigenous content.If you people still think that Tejas is not indigenous so let me take the example of Gripen.