Rebels from Yemen's Ansarullah movement announced a military operation against US Navy ships in the Gulf of Aden and Bab Al-Mandab Strait. In the Gulf of Aden and the Strait of Bab Al-Mandab, there was a collision with several US destroyers and warships. These ships were guarding two US merchant ships. As a result of the operation, the US warship was shot down. The merchant ships were forced to retreat, Houthi military spokesperson Yehya Suriyah said. The Yemeni armed forces continue to retaliate to any American or British aggression against our country by targeting all sources of threat in the Red and Arab Sea, Yehya Suriyah said in a statement. The Houthis have said their attacks are in solidarity with the Palestinians as Israel bombards Gaza. Houthi forces in Yemen have written to the UN demanding that all UK and US staff leave the country within a month on the basis that their governments are mounting assaults on Yemen. The warning also appeared to apply to NGOs working in the capital, Sanaa. In addition, it was reported that the Houthis had prevented a UN plane from landing in the strategically important town of Marib.


Today we're going to do a talk on the project that three of us worked on. We are with the Tri Valley Security Group that is a non-profit security organization formed out of the Bay Area. Just East Bay. We have Spider who acquired the hardware for us. We had Mystic here who basically kept us organized. And my name's Otto. I did the software development. The concept is we need a way to break into knatted networks. And the best way to do that is to put something inside there so we can own them from the inside out. So we wanted to place a stealth, a hostile packet sniffer on a victim network. We wanted to make it blend in, hide in plain sight, make it as a UPS. This here right here is our second model UPS. You take a look at it from all exterior purposes. It looks completely stock. We maintain the same connectivity and everything. The power switch works. It's sort of tough. Careful. Zoom in. They don't have any video, so use your eyes and zoom in. There you go. Thank you. We'll have it around afterwards if you want to take a look at it. We'll shut it down and you can play with it or something.    Those things are money to replace. So you want to plug it in and plug it into your corporate network and we own you. So let's see here. So we'll talk more about that. So like I said, today is a prototype. This is a Mark II. The Mark I was kind of ugly. And really, this isn't undetectable. I'm sorry if you came here to see the newest Uberly thing. This is mostly undetectable. Depending on what mode you put it in, it could be very, very, very quiet, but it would have no IP and you'd have to dead drop it in and then go back later and dead drop it out. If you actually wanted to exfiltrate data, obviously you have to make network noise. Someone might be listening, you never know. We're working on getting more hardware, more software to reduce the risk and increase on edge. So we've been introducing and we're going to talk about integration. I'm going to pass over to Mystic for integration. Spider here will talk about the hardware he gave. Oh, you're doing integration? Oh, okay. See how organized we are? Yeah. So then I'll talk about the software. We'll do a little demo and then we'll do a little Q&A. So if you're going to do one of these things yourself, do little case mods. Those of you who do case mods, you know about this. Ampskill.  So if you're going to open up stuff or get live power, keep this in mind. Okay. Okay. One of our biggest goals on this UPS unit was to make it look as stock as possible. I actually worked for an embedded computer company in the Bay Area, so I had access to a lot of really cool equipment, but a lot of things that people don't understand about embedded computers are easy to use. Embedded computers are basically an entire system that's been miniaturized into one system. My apologies. Okay. An embedded system is an entire computer that's been modified to fit into a very small space. The board that we're using in here currently houses a Pentium 166 with 128 megabytes of RAM and a... Sorry. What? Sorry on it. Okay. And a one gigabyte hard drive. I mean, you can attach any laptop hard drive in there so your storage capacity is unlimited. So really one of the most important things when we're building this unit is to keep it looking out from the outside as stock as possible while on the inside getting the maximum functionality and getting everything to run as smooth as possible. All right. There was four things we needed for this design. We needed obviously the UPS, the box itself. We basically stripped out the entire insides, the battery, everything that was in there and replaced it with our stuff. So this isn't a functioning UPS. It really is just deployed. It just is hard to, you know, hard to see and no one really thinks to look inside a UPS for anything hostile. It's a lead case mine. The power supply is just used for taking our AC voltage and converting it into DC. All computers run on DC. Embedded systems especially. There's only a couple voltages that computers really run at. They're either running at 5 volt, 3.3 volt or 12 volt. So as far as power supplies go, I mean eBay is a great place to pick up really cheap power supplies. If you're doing any work with electronics, you know, computer equipment, having power supplies just handy, small compact power supplies is really useful. Okay. The other thing you can do if you don't have a lot of money, embedded systems, you can start looking at them for around $200. But a lot of the times I know people want to get it even cheaper than that. HP has made a model of machines called the e-machines. I'm sure a lot of people are familiar with them. The e-machines are basically like a really tiny computer that HP made and the really nice thing about them is if you look inside, they've got an integrated motherboard that has everything included in it. So you can go on eBay and pick up like one of these e-machines for $30 and go and rip the motherboard out and you've got basically an embedded computer for $30. You want to get back on? Sorry. Oh, there's some pictures of our first prototype. As you can see, it's a lot bigger and it was hard to mod. But really the first prototype, we just wanted to make sure this idea was going to work before continuing on. Auto actually was responsible for the design of the second unit here. Okay, the board that we've picked to use comes from Contron. If you want to get into embedded computers, I'd recommend just visiting some of the sites. We've got some links on the CD. We picked this. It's a Pentium 166. It's got 128 mega-gram in it. We've got two IDE channels so we can hook up to four devices. We can have CD ROMs. We can have extra hard drives. Really, when you're dealing with embedded systems, you are dealing with a PC. There's no reason to think outside of PC terms. It's really just the form factor and the way that it's been connected together. A really good example of this is embedded computer people will know a term called PC104. PC104 is basically an isobus, but we've carried it out into an embedded form factor. As far as it's concerned, the timing, everything's identical to it. The chipsets, you know, you're using chips and technology, 69,000s, you're using all-in-one. It's just that you're changing the form factor and you're changing the size of the unit to fit into an application. Our embedded system had only one Ethernet. That was mainly because I got the system for free and we didn't want to spend any money on it. Just because we wanted to keep it simple, we just ripped a 10-100 hub and placed it inside here, which just allowed traffic to go through it. Yeah, I made this slide, so it's kind of important. One of the problems with putting a hub in there instead of bridging through, well, it's good because even if the EPS, the embedded machine is still booting and it's not being told to bridge, your victim will still get through and you won't impede his traffic. But the bad thing is you can't do proxy architects. That'd be really cool, where instead of the client going out on his MAC address, if you can bridge it through your box and then everything goes on your MAC address, you can effectively take over his IP. That was a mode that I wanted to work on for the con but didn't get it in time because we couldn't do a bridge through the embedded machine. So if we could have done that, it would have been almost impossible to tell the victim traffic from our traffic because it had been exactly the same MAC address. So maybe next year. The ugly part is that you get a link from a UPS and I was supposed to do that.  So the bridge runs, the box just runs in premise cruise mode. Yes, the embedded machine itself has a variety of different processes running on it that all make the interface go in premise cruise mode. I'll talk about those in just a quick sec. Okay, transition to software now. I used Red Hat 7.2. I know people don't like Red Hat, but sorry, I know it works. 7.2 was the first one that had the EXT file system, the EXT3 file system, the journaling. So I can yank at the power supply and it just dies and it doesn't really hurt the hard drive too much, which is kind of cool. I used a lot of scroll scripts and shell scripts and then added neat fun tools. I used Netcat by Hobbit. That's like standard issue these days. The core of the unit as far as actually acquiring victim traffic and it's a really cool tool. I recommend you check it out. Of course we use Nmap by Fyodor and at the last minute, I threw in the hacker's choice, the TCHRU there for network discovery works great. Okay, so many things still hot. This is used for basically for the plumbing. I wrote the scripts. I wrote them without any network code in them just to make it easier and I basically just Netcat everything. I used it over UDP53 which to a normal firewall would look exactly like a DNS request so it would let it through. The problem with a DNS request is not really DNS. It's encrypted but it doesn't look like a DNS request so an IDPS or an IDP system would notice this. This is not UDP, DNS traffic doesn't even look like it. If you sniff this traffic and then you use it's real to read it, it will go 10,000 requests, 5,000 replies and it's one packet. So tunneling alternatives. I could be more elite and then do port 80 TCP and actually mask the UPS requests and HB URLs and have the replies be web pages. At the last minute, I also found some really cool Perl scripts out there on the web that do exactly this but I didn't have a chance to integrate them. Another alternative, I really do like DNS because they use packets, that's a real issue. No one uses internal DNS. They always allow it out.  But it would be really cool if I could make you look more like a DNS request to DNS replies but that's next year. So back on the D sniff now. This is an incredibly cool and it's actually kind of old. It's been out for a couple of years now so if you haven't heard about it go and find it. You might need to do a little tweaking to the Berkeley path because they're expecting an older version of the Berkeley so we were set. Here's the tools that we use from D sniff actually on the box. Use Mac off. In the D sniff suite, the Mac off is actually the port of the Perl script Mac off. It starts spamming out a whole bunch of packets with forged Mac addresses. This allows you to break open a typical switch. Switches have CAM tables that keep track of every Mac address on a physical interface and they only have so much buffer space to hold those and if they overflow that they go I can't keep track of all these stupid Mac addresses so I'm just going to put everything down this port. That basically gives you access to the traffic transfers and the entire switch. It's kind of cool. D sniff. Clear text authentication extractor. It decodes approximately 20 to 25 clear text protocols. Pop3, telnet HTTP off. SNMB. SQL. It's brutal. Files snarf does NFS interceptor. If someone copies an NFS file across their box it saves a copy of the file locally. Email interceptor is mail snarf and we actually have a little test of that we're going to show a little later. I had already ran this earlier and snarfed off some email so I'll show you how that looks. Interceptor is URL snarf and instant messenger is MSM snarf. Of course the hackers toolkit thanks for your rock. It came with RPMs so we didn't have to do anything. We use it for the network connectivity with the box to make sure it can actually call out. If it can't call home it won't try to. Then I made a whole bunch of Perl scripts. The first Perl script is the master control script.  This is what it does. When it boots up it loads the config. I don't use the Red Hat network configuration scripts. I just used everything myself. That way it has a unified interface for the different modes that I use for IP addresses which I'll talk about in a second. It configs the network. Make sure everything is good and then tries to call home. From there it does an endless loop. Calls the home, works on what it gets. Calls home every number of seconds. The IP we have four different modes. Mode number one is what I talked about earlier when I said that it's almost undetectable. That's no IP where it won't respond to anything. It sits there and it sniffs. You have to be able to sneak in, put the box in place, hope it comes up okay and start sniffing. You have to turn on all the sniffing you want ahead of time and hope that your hard drive doesn't go full and come back later and get it. That's really stealthy but it's not really fun. You have to go in twice. Fixed IP mode is really good for testing. Here's your IP. DCP mode is not very stealthy though because if you're on a network that doesn't have a DHP server or they don't have a lot of nodes and they have registered MAC addresses for all their DCP nodes and they start asking for an IP address. They're going to know who's this. That's not very cool. Mode four was the most elite mode but it's also extremely noisy at layer two. It actually will... Well, here, let's do this. It watches the network for ARP requests. At first it starts listening for ARP requests and it listens to the requester. Obviously if I hear an ARP request from someone on my wire that means that they're on my local layer two subnet. It takes that IP as a seed. It turns around and uses the Hacker's Choice RU there. For that you can generate ARP requests for anything you want. I use it as a seed. I do a Class B. That's typical. Most networks should be less than a Class B and it doesn't take that much longer to do a Class B than a Class C in this way. You'll get supernets this way. The Hacker's Choice TEC RUT it can do 3,000 ARPs in parallel. This doesn't take that long. Maybe 5-10 seconds for a whole Class B. It's brutal. It'll do ARPs for every single IP in a Class B segment that it detects from the top part and then it sees everything that's there. It finds an IP that's not in use. It's in the range and just picks it. That's kind of fun. Another thing I didn't write in here, the next thing it does is then it turns around and it listens again for more ARPs but now it listens for who they're asking for. It counts about 20 or 30 packets. It's listening for who is everyone trying to find. Nine times out of 10, the most popular ARP target on a network is the default gateway. We do a little statistical analysis there and say the top one is the default gateway. If it doesn't work, the whole thing has a check here at the end where it'll try to go out, try to go out, tries to contact the listening post even. If it fails, it comes back here and starts again. Another cool thing about mode 3, the DHCP mode, if you do set it for mode 3 and there is no DHCP server, there is no spoon, it'll keep the fact that it's in mode 3 so it'll always try DHCP but if it can't get out, it'll try mode 4 as well, which is kind of fun. And there's other neat stuff, little house cleaning scripts, that kind of stuff. The actual... Let me just skip ahead real quick and show you the concept here. So you have a UPS behind a firewall and you have an attacker out there anywhere on the internet. You also have a listening post which can be the same as the attack but you can allow it to point to different directions. The UPS will add intervals, try to contact the listening post. The listening post is actually a command queue server. It will... It can actually support multiple nodes and when a UPS calls home, it will then identify itself by its node. The listening post will say, do I have any commands for this node? And if it goes yes, then it feeds the commands one at a time and each time the listening post asks for the next command, it comes back down. When it's done, it says I'm done and disconnects and it then goes to sleep for a specified amount of time and then tries again. One of the commands is call this guy and the call this guy by default is TCP port 80 and since the connection is being initiated outbound through the firewall, generally that's permitted too. Not a whole lot of people have proxy servers behind them so they'll allow clients to go out on HTTP. So I have a deal set up where it connects out to the attacker on HTTP. Again, thank you, Netcat. And provides the ConnectE with Bashel. Something that wasn't there in my connection structure and you just want to get something done, there you go. So we'll back up here a little bit. So now that you know what the client server is, what I'm talking about here, this is the DNS-like beacon that goes out by default every 20 seconds, but it's user-setable. It's desencrypted, it has randomly generated keys for each session and there's also a pre-shared key system. Each side has a pre-shared string that they will do an MD5 hash of real quick and then use that along with another randomly generated string and put those both together as the actual crypto key. They only exchange the first part, the part that they randomly generate on the fly for that session. It's not the pre-shared secret ahead of time, so even if you see this in flight and you see a key is going back and forth, you still can't decrypt it because you don't know what the pre-share is. That's kind of cool. So the client connects at intervals control, the master control script to the server, the check to command queue for changing the configure behavior. Like I said, it goes out of our UDP for configing and then a reverse shell on TCP-8-ing. Looking towards next year to add attachments to send out SMTP as well. That's a really good expectation, but I just didn't have enough time to finish it. So you saw this, it's pretty. So in the listing post, of course, SSH, so you can command to it. Just real quick, this is uh-oh. It's not happy. Oh, no. So there's what the encryption looks like, by the way. Actually, that's the key exchange. My listing post thinks it's trying to send data, and it's the LP is trying to send its key instead, so it should recover here in a little sec. But anyways, we're not ready for that yet. Oh, yes we are. That rocks. So okay, so I want to switch over to the victim here. Okay. So what died? Okay. I'm answering technical difficulties, please wait. Thank you. Okay, so something unplugged? Just a moment please, thank you. Sorry.


excited to introduce our next speaker here. She's somebody that I met, well I met Brenda 12 years ago when I was a we undergrad, Carleton University, walking around thinking I knew a lot of things, and when I met Brenda she explained to me many different times in many different ways that there's a lot more to know, and it was one of the most important lessons that I learned while I was here at Carleton as you know we only hold one piece of the story as an important piece, but it's only one part of the story, so I have something to read. Brenda since 2010 has been the Chair in Matri Research at the University of Ottawa, where she also holds an associate professorship in the Department of Geography. Her career has been spent studying Mati history and culture from the inside, seeking ways to express Mati history from the perspective of a Mati worldview and set of understandings. She works to understand traditional kinship practices as the foundation of all social and political behaviors within Mati communities, and throughout the course of her career she's worked in Mati communities in North Dakota, Ontario, Manitoba, Saskatchewan, researching their histories and documenting the connections and relationships between family members as a lens to understand both Mati society. So I'm really pleased to introduce Brenda McDougall. Yeah, you wanted left, remember? Thanks, Benny, and thank you for coming today and for the opportunity to speak, and I was really excited by listening to David this morning. So I'm in a geography department, I'm not a geographer. I'm actually trained in native studies with a historical background. So I'm a bit of a fraud there for that little bit. And because I'm a historian, I actually don't do ethics research processes. I don't have to go through research ethics boards. I don't have to fill out the forms. I don't engage in any of that and I'm pretty relieved not to do it. I've helped my students through the process and I'm happy I've not done it myself. But I don't want you to think that because something is historical that somehow that mitigates you from having a responsibility to think ethically or to behave ethically with archival sources and with the lives of the people that are found inside of archives. So while technically I don't work with live human subjects as described in ethics applications, I work with the dead, I very much feel that I have a responsibility to the families, to the individuals, and to the communities that I work with because I'm writing their history. I'm trying to track down sources that they have left or that have been left about them that reflect something about who they are. And so I wanted to spell a couple of myths maybe. And one of them is that we didn't leave written records, that indigenous people don't leave written records. We have lots of written records. We need to start paying attention to the archival traces that we created, that our ancestors created, and not ignore them. That doesn't mean that we don't use oral tradition or that we don't work with our elders or learn stories. But we also have to consider the legacy that exists within the archival repositories spread across this country, spread across North America, and sometimes in Europe. So the material I work with primarily is, in fact, church records. I rebuild genealogies. And I do that as a way to try and get at how people lived relatedness. How did they function in a community of related human beings? What does an extended family kinship look like? How does that extended family kinship spread out over a geographical space? How do families break apart and come back together at certain times of the year? Or maybe a generation later? And what does that mean in terms of their processes? So while I don't follow a formal ethical process in an institutional way, I work with traditional people from where I'm from. And so the very first teaching that I received became very much a part of the first research that I ever did, which is Huakotuin, the idea of all my relations. So Huakotuin is a Kree word. It was taught to me in Saskatchewan. I probably only know a little bit about what it actually means. But the basic principle is we are all related within our community. And that the process of building community and then in turn of building nation is to go out and create relatives. And the most pitiful human being in the world is one who's alone. And so to go forth and to create as much family as possible. So this notion of an extended kinship as opposed to a nuclear family. That's the first place that you have to start with if you're working with an indigenous worldview. Certainly if you're working with a Métis worldview, is to start considering not just the parents and the grandparents and the kids and the grandkids, but who are the aunts and uncles? What does the auntie look like? What does the uncle look like? Who are all of the mushums or grandfathers in the community? Who are all the cookums in the community? And how do they interact with one another? And believe it or not, you can find this material in archival sources. There is a there's a deep rich legacy of information about indigenous family structures within archives. One of the principles of Huocotun is reciprocity. So reciprocal relationships, looking after one another without an expectation of anybody looking after you. But because you are generous, because you are kind, because you have good intentions, people in turn will look after you if they can when you are struggling. And so, B Medicine, an anthropologist, a Sioux anthropologist from South Dakota, did a great deal of writing about the reciprocal family nature that is inherent across indigenous cultures, but she of course focused on her community, the Dakota Sioux. And another, there's some, you know, this is where indigenous writers, right, she's 20th century, but a 19th century indigenous writer was Ella Cara DeLoria. She's the great aunt of Vine DeLoria, if you've ever had to read Vine's work in classes now.  Right, so our very humanity is embedded in family. And we are not humans, we are not fully human, unless we understand our relationship to people. But it's not just a relationship, it's a responsibility. Right, so we talk about indigenous rights, which are important conversations to have. But we also need to talk about what our responsibilities are to one another. Because if we don't enact our responsibilities, our rights don't mean anything. And so reciprocity, humanity, responsibility, and, and fundamentally being respectful. And if you show respect, you receive respect, that's part of that reciprocal relationship. It's not just things that you can that you can support people with, it's the respect that you can show them. That is reciprocal. And so by thinking about these things, every time I pick up an archival document or try to understand somebody's historical behavior and actions, if I start to think about these things, I get a sense of how they made decisions. Right, because it's one thing to, to know facts, you know, we can all know facts. Leroy Riel had a resistance in 1885. That's a straight up fact. Why did he do it? What was his motivation? What was his, what was his thought process as he did these things? Those are the interpretive frameworks that we put around historical content. And as we know, indigenous history up until maybe the 1960s was written primarily from a Western white academic lens. And so people's motivations were always framed within those Western frameworks, as opposed to within an indigenous framework. And more specifically within the framework of the place that they came from, the nation that they belong to, the community that was the foundation of their relationships. So you start in those places and start to work your way out in terms of, that's that's my process, right? That's, and, and so my ethical responsibility in that process is what are my values? I believe in Wakotuen. I believe in these structures. I was raised within them. I didn't know the word for it until I was an adult, but I understand them. And so what is my responsibility? What is my reciprocity? And as long as I carry those frameworks with me, I'm an ethical person. So you can institutions can mandate things. But if you don't, if you don't behave ethically, if you don't have it in you, it doesn't matter what what any institution tells you in terms of what the rules are. You'll find a way to violate them. So they're a nice guideline, but you actually have to embody it first. So I do genealogy, so I'm gonna, I'm gonna walk you through this family. I'm not gonna. So this is a pretty standard genealogy. And, and I'm gonna do this to try and explain and give examples of some of the things that I mean about what a worldview functions or how it could function. So this is the family of Elizabeth Monroe Fisher. She's at the bottom. She's a little bit bolded off to the side there. She she's from the the great the South Southern Great Lakes region, her family, the fishers, but her extended kinship, which includes Lafomboise, Langlades, host of other families. They exist since the 1700s between Michelin Mackinac, which is now Mackinac Island in Michigan, Green Bay and Prairie du Chien on the Mississippi River. And so Elizabeth is one of my favorite people. I have lots of favorites. But she's one of my favorites, because she actually wrote her life story. She wrote newspaper articles about what she referred to as the old pioneers of Michigan. She wrote about her family. So she she embedded them within this narrative of being a pioneer of being an original settler to a place. But if you actually start to read her memoirs and then place it within the framework of her genealogy, you start to see that she's actually telling the history of Adelaide and Ojibwe women and their relationship to fur traders over time. And so she she doesn't ever name her female relatives, but you can actually start to pick out who she's talking about based on the life experience as she describes it. So just to give you a sense, this is Elizabeth.  And this is four generations of her family, her daughter, her granddaughter and her great granddaughter. About the 1890s, 1880s somewhere in there. So Elizabeth was born on the 24th of April in 1810. She starts to appear in the historical record when she is baptized in 1821. So she's baptized almost 12 full years after she was born. And and her birth certificate actually is a really long notation about how that came to be. And so it's a really interesting document. She was baptized at St. Anne's in Detroit. She was baptized in front of her mother and her godparents who were named as Joseph Roulette, who eventually becomes her brother-in-law and Madeleine Lafombois of Mackenac, who is her great aunt. The notations in this baptismal registry state that her father, Henry Monroe Fisher, is not present. And tracking him down, well, he's not present because he didn't want to be involved in the War of 1812. So he went to Red River. So he was actually further west at the time that his daughter was was baptized. And he actually never saw her from the time that she was two years old, until she was married in 1824, I believe at the age of 14. You might be able to read it closer. I'm not quite that. It's very small. So Henry and Henry Monroe Fisher and Elizabeth's mother, Mary Ann, were married by a civil judge. So they weren't married in the church. This is all in the baptismal registry. And Elizabeth was originally privately baptized. So somebody in the community baptized her at birth. But she didn't, there was no opportunity to see a priest until they went to St. Ann's. And Henry Monroe Fisher is described very clearly as not being present at the baptism. However, Fisher is a prominent fur trader. He started his career with the Northwest Company at Mackinac or Michelin Mackinac. He continues to trade for the Hudson's Bay Company in Red River. And a whole group of his descendants actually end up in the Quapel Valley of Saskatchewan. I first met Henry Monroe Fisher, and I always describe them as meeting them, because I feel like I know a lot about them by the time I actually read something. I first met Henry Monroe Fisher, even though he's been dead for a very long time, through one of his great, great, great granddaughters in the Quapel Valley. She told me all of everything that they knew in the family about the fishers. What she didn't know actually was about Michelin Mackinac, and she didn't know about the connection to the birds. So I've been able to go back and provide that kind of information to the family in Quapel by knowing this stuff in the east. So that's also, I think, part of the ethical responsibility of behavior is giving things back, right? So I was fortunate enough to be told these stories. She was a student of mine. She was just sharing information, and so I made sure that I had a way of providing that back to her. And I've done that as much as possible. Sometimes it's hard when you lose touch of where people moved, but, you know, it happens. It eventually happens. It all eventually comes back. So just quickly returning to the genealogy, Henry Monroe Fisher's first wife was not Elizabeth's mother, but was, in fact, a woman by the name of Madeleine Goche. And Madeleine is the daughter. She's a French Adawa descent, and she is the daughter of Fertred and an Adawa woman. And most of these people are, in fact, descended from the Adawa nation. So this is a form of maintenance that comes out of the Adawa as opposed to Cree or Dene, further west, or Ojibwe. But through the interconnections of all of these families, we start to see a network of trade relationships. We start to see a network of relationships into First Nations communities. At the same time, we start to see the evolution of a distinct community. As people start to move away from their European and First Nations ancestor and start to live amongst themselves and interact amongst themselves. And central in everything I've ever done on Métis people is the core of women at the kinship network. So they're not, you know, they're not just mothers and grandmothers. They're actually the people that are holding the entire family structure together.  Or is the crazy relative, right? There's an explosion of genealogical interest these days. And what that might mean. And people, you know, spend a lot of time on ancestry. I do too. Sometimes I just lurk to read the comments. Because they're so interesting. I don't, and by the way, I'm gonna help myself. I don't know much about my own family. My sister does that. So I get to dabble around in other people's information. So and I kind of, you know, it's a puzzle. I kind of enjoy this. But I'm being a little sidetracked by not focusing. So what we start to see is this core group of women. She talks a lot about, she almost never talks about the men that she's related to. She always talks about her mother, her grandmother, her great aunt, and the women going back in time. And so there's this idea that we don't know a lot about indigenous women. It's very much like the notion that we, you know, we don't leave written records. It's a myth. We actually know a lot. We just actually have to pay attention to what people are saying. We have to listen. We have to read and we have to ask questions. And they're all there. But it takes more time. It's really easy to know the history of Henry Momnero Fisher because he's a fur trader. It's very easy to know the history of Charles Langlade because he's a fur trader. And because they leave these long histories of economic and political and military types of behaviors. And because historically men wrote about men. These were the stories of great men. And I'm not saying that there aren't, you know, really wonderful scholars now who are male who do female history. Of course there are. But the foundation of history is great men history, right? The kings, the emperors, the, and then it just sort of trickles down from there. So this is about getting away from that idea of a great man. Even in indigenous history, we don't need to talk about great men. We need to talk about what the kinship looks like. Because those men have power because of who they're related to. So fur traders go off and they do their thing. They might, as Henry Momnero Fisher did, he might start in one place and end up in another. His family never left the place that they were from. When Henry Fisher left to go to Red River, he took two of his sons, Alexander and Henry Jr. And he left his daughters behind with their mothers.  And it's through Jane that she becomes the sister-in-law of Joseph Roulette. And so it, her God father then gets reincorporated into her kinship system via her sister. And so when you do, if you ever engage in Métis genealogies, you're going to see a lot of this fold over. Paying and using sacramental records is important because finding out who the God parents are tells you more about that extended kinship system. Because these are not random individuals that are chosen. These are people that are very important in the community that then knit and bind people together over time. So I've done analysis, analyses of God mothers, for instance. How, how often one woman might end up as a God parent to a series of children. And I've, at Michelin Mackinac from early 1720 until maybe 30 years later, there are several women who are God parents to thousands of children. First Nations, Métis, and French or Scottish. So these women, you have to think, if they are serving that often as Godmother, this is phenomenal information. This tells us something about their prestige. This tells us something about how the community saw them and how they were responsible for all of these people. Because God parenting, of course, is very serious in the, in this era, right? This is an important position. This isn't, you know, an accident. You are responsible for the well-being of these people that you agree to be a God parent to. So two people figure very prominently in the stories of Elizabeth Baird and her, her stuff is online at the Wisconsin Historical Society, actually. You can actually read everything she wrote online. But she talks a lot about Mrs. Lafambois and Mrs. Schindler. Trace Schindler is her grandmother and Madeleine Lafambois is her great aunt. And these women were powerful traders in their own right. Both of them were widowed. They had been married. Madeleine was married once. Her husband was murdered. And she took over his trade and built an empire of trade on Mackinac Island. She was prominent in the War of 1812. And she is, I would say, single-handedly responsible probably for all of the Lafambois that exist across Western Canada now. And there, and in the United States they're the raspberries. There's a whole branch of families known as the raspberries. And Trace Schindler, she became Schindler by her second marriage and he died. He got ill and died and she took over his trade. So the idea that women didn't have an economic role or that it was sort of confined to what is typical of being female, whatever that, you know, might historically be defined as. I see examples all the time of women who trade. In Western Canada women who buffalo hunt or who control the caravans. So these are jobs that are open to women. And in particular women who seem to have an ability to build networks of relationships and work very hard. Madeleine eventually retired from the fur trade. She sold her interest in the fur trade to the American Fur Company and she opened a school on Mackinac Island because she, while she could not read or write, she wanted children to be able to read and write. And her sister Trace and her niece, Elizabeth's mother, worked in that school and they worked with children. So I never expected to study women specifically. I never expected to study kinship specifically. But these were the teachings that were given to me by the by the elders that I work with in Saskatchewan. And so this is the place that I ended up. And I think that's also one of the responsibilities I have then as a scholar is to follow the path that they've been laying out for me.  So I'm happy to do it. So when I was trying to understand what Kothuin though, I wanted to know what some of the traditional stories might be around it. And so there are all of these traditional stories about humans marrying animals, you know, in the time before now. And so I was really excited because this book came out of Labrador last year, The Man Who Married a Beaver. I'm familiar with the story of the woman who married a beaver. So it can be back and forth in gender. The beaver stories tend to be in the east. If you're on the Great Plains, there's relational stories with buffalo. If you're in the north, it's probably more likely caribou. But I've also heard stories of people who are married to dogs. Dogs are so important in traditional culture that some of the earliest stories are actually relationships to dogs. And so I became a little bit obsessed with the story of the woman who married a beaver because that's the first one that I encountered. And I've read most of the translations of it. I've asked people about it. And I'll just tell you really quickly and abbreviated synopsis of the story. There's a young woman who went out to fast on the land and after a while a young man came along and interrupted that fast. And they spoke for a long time and he eventually over the course of that conversation asked her to marry him and to come away with him and live with him. And it took a little bit of persuasion, but the young woman eventually did go to live with him, sorry, and left her family. She thought he was kind. She felt he was a good provider. She really quite appreciated him. He asked really only one thing of her when they when they went back to his lodge. And that was that she she actually not contact her family again, but that she stay at the lodge with him and that he would then provide her with everything that she could ever want. He would bring her cloth and tobacco and silver jewelry, beads, ribbons, pots, any kind of metal implement, including knives. Anything she needed, he would he would make sure that she never and food, of course, she would never ask for anything. And that she and she was happy with that as a young bride. And as a woman, she had children. She was very content in her new life. She was happy with the children. And so she was happy to to grant that request for their marriage. And as they grew old together as her children matured, she did start to think their behavior was a little bit weird or strange. Maybe that's a better word. And every so often they would leave the lodge, they would go out amongst humans, they would get some of these things that she had asked for, ribbons or mirrors or whatever. And they would return home and they always came home with these new very lovely things. And she never really asked about it, but she just felt it was strange. They could be gone for days, they could be gone for months, and then all of a sudden they would reappear. And it took her a few years to finally figure out that she was in fact married to a beaver. And she was living in a beaver lodge and her children were beavers. And what was happening when they went out was that they were sacrificing themselves to hunters. So they would be hunted. And hunters were responsible for leaving all of those gifts for the beavers as a part of their ethical responsibility when they hunted. So they would leave tobacco, they would host ceremonies, they would feast properly, and they would leave all of these gifts and offerings to thank the beaver for giving up their lives. And really what was happening here was the basic foundation of family. This is all about the reciprocity. And it starts in this place. And so one day her kids got married as they do, they went off on their own as well. And her husband and she grew old together. And he finally died and he never came home. And so she was in the lodge and she was thinking this is longer than he's ever been gone. Not really sure what I'm supposed to do. So she sat there and she waited and started to think about what she might do next. And then she heard human voices outside the lodge. And so she called out to them and these hunters broke through the lodge and they pulled her out and they were surprised to have, you know, pulled out this elderly lady. And I imagine that she looked something like this. It's described that she was, had silver hair, that she was covered in silver jewelry, that she had all of these beautiful clothes and adornment. And so she realized at that point in her life that her job now was to go back to her own community and to talk to her community about the relationship that they would have with beavers. That the issues of reciprocity, that as long as you looked after your relationship with those animals, they would provide themselves to you.  They weren't being respected any longer. And so she spent the rest of the remainder of her life giving these teachings. And these are the fundamental teachings of family, right? The fundamental teachings about how to be a good relative come from this story about the woman who married a beaver or the man who married a beaver or whichever story or narrative you want to follow. And so it's a fundamental teaching. It's a fundamental reflection of Huacotun, to understand this and to behave as properly as you can, to learn the lessons of being a good relative, of being a human being. And this really provides a narrative framework for understanding how relatives are expected and encouraged to behave amongst one another. It explains the mechanisms for creating family, right? You get married, you have children, but you don't separate yourself from those people. And so embedded in the story is a blueprint for a healthy life, but it's also a warning. It provides the warning about the consequences if you don't live a healthy life. And so these stories tell us about the ethical responsibilities that we're supposed to have to one another. So I'm going to leave you with one more family and genealogy to sort of reinforce maybe some of this. Of course, I'll answer questions. So I'm going to pronounce La Liberté the way that they pronounce it at home. I'm from Saskatchewan. And I know a lot of the La La Birdie family. That's how they pronounce their name. I actually never realized it was La Liberté until I came east. Of course, I can read, but I'm used to the La Libertés. So this is one of the first families that I started to work with. They are from Northwestern Saskatchewan. So Northwestern Saskatchewan, as a fur trade region, was known as the English River District. It's the entire west side of the northern half of the province. So from Green Lake in the south, if you ever look at a map and I didn't bring one, Green Lake is the southern boundary and the northern boundary of the English River District would be what is now the border with the Northwest Territories. And it extends across the Alberta border into places like Cold Lake and the Athabasca. So it's sort of, it's fairly, but now it's, you know, the province comes through. So Alberta Saskatchewan kind of divides up the old territory. The patriarch of the family is Pirish La Liberté. So I'm going to start with him. He's a fur trader. He was not literate. He never wrote any documents. But he's described a lot in Hudson's Bay Company records because they got annoyed with him. And whenever you're an annoying person, people write a lot of things about you.  And it was only in reconstructing the genealogy that I, that I saw the way that some of the, his children behaved as well. So in 1890, Pirish La Liberté was 73 years old, still working. He had married Sarah's in back in the early 1830s, late 1820s. And Sarah's in was born in the Northwest. Pirish was actually born at Prince Albert. You've ever heard of Prince Albert's Saskatchewan? That's marked as the north. It's not the north. That's just sort of the gateway to the north. But Sarah's in was born up in the La Loche district of Saskatchewan. Anyway, in 1890, when he was 73, he was the father of nine children. And he announced to the Hudson's Bay Company at Isle of Cross, which is the district headquarters that he wanted to retire. He felt he had done his time. He was a postmaster at Portage La Loche, or La Loche now, and La Loche was in the news. So it'll give you a sense of where it was. This is where the school shouldn't took place in the north. And so this branch of the Lalliberty family had always sort of been in the La Loche district of the English River District, so very far north. And La Loche is important because it is the last fur trade post before you cross the Athabasca, before you cross the height of land into the Arctic. And so it's a staging site for voyagers to transfer goods and furs. So it's one of the most important places in the English River District trade system. And the man in charge of the post is, from Western standards, illiterate. He doesn't read, he doesn't write. He can't keep the post journal, which is part of the job of a postmaster, one if his son-in-law does it for him, because he can't do it. So he wants to retire. He wants to go south. He wants to go to Green Lake where some of his sons are working, where some of his daughter-in-laws are from, and he's going to take Sarah's in. She's still alive. And he also has a plan. It's kind of one of those retired but not retired situations. What he wants to do is he wants to move freight between Prince Albert and Green Lake. And he wants to work with his sons in this freighting business. So he wants to open his own, he wants to be an entrepreneur and do his own thing. But he also wants a pension from the company which he has worked for for 50 years. So the reason he's so represented in the records is because they're talking about this pension. So they give him a pension, reluctantly give him a pension. Companies are cheap, even in the 19th century, maybe worse. They reluctantly give him this pension. And they expect that when he's working he will look after their interests and not work with competing companies. And there are competing for trade companies. So he says, okay, I can do that. So he moves to Green Lake, Sarah's in goes with him. And he begins this freighting business. So Sarah's in descends from this family. She's the oldest daughter of Antoine Morin and Pelage Boucher. Every Lalliberty and Morin in northern Saskatchewan descends from these two particular couples. That's your surname. These are your great grandparents. So it doesn't matter if you're on a First Nations reserve or if you're in a Métis community, everybody descends from these two couples if you hold those two surnames. So let me tell you, I get a lot of calls from people who have Pelage Boucher in their family. And they want to talk about her. I don't know very much about her because she is a little bit enigmatic, but she was born on the Athabasca in the early 1800s. She is very likely the sister of a woman who married into the Riel family. And so Louis Riel's line comes from her sister. So there's this network of families. This is the other thing about Métis people. There's this idea that somehow it's this random collection of people. These are really intricate webs of kinship that Métis exist within. This is not random association. These are not just mixed blood people, quote unquote. These are people who are embedded in networks of kinship over time in generations. When I did the work on northern Saskatchewan, I found five generations of families that were intermarried with each other. So back to these guys. So Peerish and Sarazan by the time 1890 rolls around have 13 children. Not all are still alive, but most of them all are. Most of them continue to live in the English River District. Only one son went further east to Cumberland House to trade. That's Antoine who's married to Matilda Collings. Everybody else functioned somewhere between Meadow Lake and La Loche. And they are intermarried with Cree, with Denae. They are French. They are Scottish. But they function as a solid integrated family unit over time. All of the sons become fur traders. This is the other thing that's kind of key to Métis history. Sons become fur traders. You're the descendant of a fur trader. You work in that economy. Daughters marry fur traders. And so it becomes an economy of scale that is also an economy that is a uniting factor in how people behave and the choices that they make. And so two years after he retired, the Hudson's Bay Company starts talking about him again because he's actually trading against the company's interests.  Some of them are starting to do their own thing as well. So he's got one son who's supposed to be managing cattle on the Métis Partage. He's got two other sons who are postmasters. One who stays at La Loche. One who's at Green Lake. And several more sons work out of Ilocross proper. And so as they're having this discussion about whether or not they should cancel the pension because they're actually earning their own money now, the chief factor at Ilocross actually says about peer-ish, and this is I'm just going to quote this directly. He has a huge part of his family married and settled in the vicinity of Green Lake. And by his keeping a small stock of goods, which are actually sold by some of his sons under his inspection, his sons are kept from taking outfits for trade term to oppose the Hudson's Bay Company from the merchants at Prince Albert. And as we gain by the transactions in more ways than one, it's advisable to allow him to keep his pension. So in fact, although he's violating the terms of his pension, although he's irritating to them, he continues to receive his pension for another five, six years until he passed away. So the influence of peer-ish as the patriarch of this family extends to his sons, but it extends past his sons to his wife's relatives, the morons. It extends into the Cree and the Denei communities. And he's actually able to keep control of a large part of the fur trade either for himself or in a way that benefits the Hudson's Bay Company. And he's able to mobilize these things not just because of what his sons do, but because of the strategic choices they made when marrying their daughters off. That's the wrong way to say it, but it came out that way. These are all arranged marriages, right? These are not random. These are not love matches. There's no such thing as a love match historically. Maybe now. Granted that. But these parents are picking who their kids marry. And they're making very strategic and controlled choices about what alliance networks they want to extend themselves into. So my last thing, a couple last things. So this is just to show you how complicated it can get. These are just like, this is the Moran and Dela Ron family. And they went back and forth and intermarried over two and a half generations. My husband was really mad at me when I made him make that chart. Because so much easier, right? But I wanted to be able to explain this. I'm not going to explain it to you. I just wanted you to see how I always sort of joke that Métis genealogy or the Métis family tree isn't a tree. It's a stump. And he came up with a better analogy. He said it's like a rose bramble. You guys just keep doing this all over the place. I mean, you're so interwoven with one another. It doesn't make sense after a little while. And it's true. Métis people can go into almost any part of this country and meet somebody that they descend from the same people from. And it creates this instant connection. So I want to make a little plug for archives. So this is William Henry Jackson. This is actually one of my favorite photographs because it's just so, quite frankly, so damn sad. He was the secretary to Riel in 1885. And he knew Riel in 1860. And when he was nearing 100, he lived in New York City. And he had been keeping papers. And he couldn't keep his rent any longer. And he was turned out on the street with his papers.  So we have, think of what we lost, right? He kept everything anybody ever wrote. And it's all gone now. So keep your papers. Give them to people. And use archives. And use archives in conjunction with working with traditional knowledge holders. Because the minute you do that, it opens up a way of reading history that isn't just about writing a counter narrative, but in fact, comes from our traditions, is informed by our worldview and says something about us that nobody else has said before. So I'm going to stop there. It was a sad way to end. I know, I'm sorry. I always say I'm down. Usually people end on a high note. You took us down a sudden. I could jake. I want to thank Brenda for that. She began her presentation by saying that she thinks she may only know a little bit about Wakotuin, about that responsibility that we have to each other. And I can tell you that in the past 12 years that I've known Brenda in my personal journey, on my academic journey, I've fallen into a number of holes. And Brenda has always been there to reach down into the darkest pit and bring me back up. In times when I had nothing to offer her. And when I would ask her why she would always do that, why she would always be there, for me, she would say, because it's my responsibility. And now I'm here at Carlton in a position where I want to live in that same way. I want to help the students that come here. And I want to make them feel comfortable. And I want to be that person that can teach them about Wakotuin. So I just want to thank Brenda for that. We have time for a few questions, maybe two questions, that we could field. So I'll open it up to the room. And if anybody has anything that they'd like to ask, Brenda. Actually, which I thought was really amazing watching this is my brother married Amaran. And then divorced Amaran and married Ola Liberty. I'm not joking. I really want to know more about this tree, because it's interesting. Oh, the data project? Oh, so online, it's called the Digital Archives Database Project. If you Google that, you'll find it. I should have put the URL up. But I can leave that for people. So since I've been in Ontario, I've been gathering as many church records as possible. We have a team of students who have been transcribing them for the last seven years. And they are all available online in their transcribed form. So we're just putting online another set of records this summer, most of the Northern Ontario records, but also stuff from Michel Macanac's already online. And a lot of the Red River parishes are online. But we started working with some of the Ontario records as well, so those are available. So it's not a complete set of anybody's records. They're sort of cherry-picked by me, because they're things that interest me. But also online, along with that is my colleague, Nicole Saint-Ange, is going up this summer will be the Voyager Contract Database. It already exists online, but we're creating a new interface for it. And Mike Evans at UBC, Okanagan transcribed for trade records. So those are all online from anything east of the, sorry, west of the Rocky Mountains in the lower mainland. Thank you very much.


Hey there, Chad Bondra here for High University Libraries. Today I had an awesome consultation with a student. She was looking for some pretty difficult to find information. Basically she was looking for, I got to read it off here. She's looking for small companies with less than 75 employees with less than seven years of operation that are located in specific counties in Ohio that do manufacturing in a particular or in a particular kind of business in local areas in Ohio. So the immediate database that came to mind was a database called Mergent Intellect which is a great tool to use if you need to screen for specific company criteria and get a list of companies in your area. So this video shows you how to do that because I thought it was such a cool question that I really wanted to share with you guys how to do that. So here you go. So this is the Mergent Intellect homepage and Mergent Intellect is basically like a big phone book that contains just company information. So if we want to go and just search by company, for a particular company name, we could do that here. For the purposes of our search, we're actually going to do the advanced search feature down here which is going to allow us to screen or to search for custom criteria for our companies. The easiest way to begin our search is to search by location and for that search we're going to search by county. That's what the student was originally asking for was counties in Ohio. So we'll do USA here and then search for Ohio. And it's going to give us a list of counties. And for my example, I'm just going to choose Muskingham County as my example. And once you have one selected, you get out here and click add to criteria. And then it's going to populate how many companies that are in Mergent Intellect in Muskingham County. And in this case, it finds over 11,000 companies in Muskingham County that are in Mergent Intellect. Next thing we're going to do is look for the size of the company by employees. We're going to go and click on size. And we'll do employment. And we'll say she wanted smaller companies that have less than 75 employees. So we will do that. Add to criteria. And you can see this only got rid of like 100 companies. So that's not really a great way to screen. What we can also do is now we're going to go and limit by industry. So this will give us a little more granular search here. So we click on industry. I generally prefer to start with the NAICS code. The NAICS codes are newer. This is the way of industries are classified by particular codes here. And if we look at manufacturing, we see this is kind of more kind of traditional manufacturing. If we go and look at things like this, we see there's chemical manufacturing plastics. I'm just going to choose a section within here. It looks like they're doing a lot of computer equipment and metal manufacturing and that kind of stuff in this category. You can drill down further if you like. So if you're just looking for a computer electronic equipment, you can do that. I'm just going to choose 33 right here. And then I'm also going to look at just choose another industry. We'll choose the information industry because this will contain things like internet publishing, telecommunications, search providers, web portals, data processing, all that kind of stuff. So kind of some high tech areas in there. So we're going to click on that right there and add a criteria and watch our number here. Our number is going to go from 11,600 down to 269. So that's a lot more manageable for that area. The download limit in Mergent Inselect is about 2,000 companies. So we can't get like 12,000 companies and do a search and try to download all those companies. So we want to make sure we get a manageable set and 269 is definitely appropriate. So what we're going to do is click on all right here. If we just click on the download right here or export, we're just going to get this list here. I want some more extensive information than that.  This takes us to this screen and you can see all these sections are actually checked by default. I don't really want all that data. So I'm going to actually click on choose fields which will allow me to go in and choose which fields I want. Obviously, I want company name. I want their website address if it's listed in here. I want their physical address. I also want their NAICS code, their primary SIC code and the description. So I want to know what kind of business they are in. And we're just looking at the primary, what they're primarily engaged in. I'm also going to go in and look at here's our year of founding because part of our question was the student wanted to know companies that were founded in the last seven years. And I want to know if the company is a subsidiary of another company. And also if they are a subsidiary who the parent is. Finally, it also be a good idea to do the size. So we'll do the for sales. And let's do how many employees that they have at that current location. Once we're satisfied with that, we go down and click on we have to enter a file name here. So I'm just going to call this Chad's. Let's call it Chad Muskingham. And we will build our files. You can either email it to yourself or download your file. I'm just going to click download here.  And if we just click on the Excel file here, it's going to open up in Excel, we can look at it within Excel. So I want to enable editing here. So I can do some sorting. And what this allows you to do, you can see these companies, they look kind of random here. But if we scroll over and look at sales, we can see that the companies are indeed sorted by sales. Okay. So what I'm actually going to do is the original question was to find companies by industry that are less than seven years old, and we can't screen for year of founding. But what we can do once we have our list here, that's one reason I want to make sure we have the year of founding in our in our list of that we're building, as we can go and now do data. And we can sort it. And we can sort by year of founding, and then largest the smallest and then what do you know, in our list here, now we have the companies that were founded by your founding. And that's a good way that we can identify companies by industry within the past, you know, seven to 10 years found in the past 70 years, seven 10 years by location, a particular area. So hopefully this video showed you how you can use emergent intellect to do some really cool stuff and get really granular and get some really good information about the companies by industry by location, with less than seven years of operation with less than 75 employees, you can get all kinds of crazy stuff like that emergent select should need more help about about emergent select or any other database look for the contact link on the business blog and got to help you any way I can take care and have a great day.


We very well know the overall engine architecture with its own service stratum on top of the transport stratum the services by mainly managed by the service control function in the service stratum are mainly linked to the Way in which these services can be provisioned But there are some interesting Dimensions to the service delivery and service provisioning which need to be Incorporated in our understanding for engines. So we'll start with the concept of the open service environment We'd look at its requirements in in specific and we'll see some sample Protocols so what is open service environment? Open service environment as the name suggests is is an open interface for creating and registering and invoking and providing and Terminating services and once the service is no more needed Removing a service. So these services are basically going to be provisioned through the Transport and service stratum of course, but each service requires triple a Admission and resource control quality of service provisioning etc. Now, whatever each service requires The functionality it needs comes from the the service stratum Let's look at the overall service architecture in NGN from the Open service environment perspective here. You can see that we have the Transport stratum below. We have the service stratum within the service stratum. We have the open service Environment that contains some functional entities. These functional entities may be used all at once Maybe some of these are used then we have the application support functions and the service support functions which is shown to you as The outside block it means that the open service environment is a sub part of the ASF and SSF within the service stratum So you can see here that we have the application on the top This application is connected to the service stratum Using the application to network interface Then we have the service stratum that is connecting to the functions from other service providers through the service to network interface Other interfaces are not exactly in our scope for now, but we'll talk about them on need to do basis So you can see here. Let's name a few we have the service composition service description service management service discovery service registration Etc. Now the policy enforcement and the joint or interworking with other service creation environments are the additional responsibilities which are scope of the open service environment We can actually go from from the service composition or service creation on one end followed by the service description and then service registration by the service provider then the service Discovery can be actually used by the Service solicitor or someone who wants to use service the service management Along with the policy enforcement and the interworking with other service creation environments We can actually look at the end-to-end execution. However for brevity We are going to just consider some instances. So the overall service provisioning architecture for NGNs Necessitates certain requirements to to be met from the open service environment and all the functional entities We've seen in OSC are all poised to meet these requirements. So there are a total of six requirements Let's start with the first one that is to provide a standard Application programming interface to develop and install applications in a quick and seamless manner So the focus here is on on convenience that is Without much moderation. It should be instantaneously done. So that's the first requirement It means the standard API means whomsoever as a third party wants to provide certain services to To end users through the NGN should be facilitated through some kind of standard in interface Then the next requirement is or whatever Services have to be provided some kind of Interoperability should be supported because the networks which are connecting to the NGN are going to be different in their Intrinsic or internal design different operating systems like Windows Mac Linux etc are going to be used Different hosting platforms for service delivery and the service execution could be used Different programming languages could be used and then different web Based services could be offered each coming on certain Web description Framework, so it means that the interoperability is a very important requirement for the OSC to meet Then the service development service creation should be made independent of the manufacturers of the network and the user equipment Because whatever services are to be created have to run on a variety of Networks which could get Upgrade the technology could all together change the user equipment could be a handheld device It could be a laptop or it could be Fidget for that matter in that case it is important to Look at the service development In the absence of any dependence on the underlying infrastructure Then the service creation process has to be Transparent or aloof to the location, which could be a geographical location, which could be an IP address based location It should be independent and it should stay consistent across different geographies different IP addressing and different other addressing schemes the Networks to which are going to offer these services have to Be transparent the protocol transparency and the technology and the Terminal should be Transparent as well. It means that the service has to be offered in a very seamless and transparent manner and This can only be done when a standard API is provided which hides the Network complexity from the eyes of OSC then Whatever services are to be offered service management capabilities have to be met that is a service has to be made a discoverable service has to be Defined or described through service description then the live monitoring of service Like service tracking has to be ensured some kind of updation version control have to be implemented and authorization to use a certain service or Refusing has to be incorporated as well Then the services which have to be Provided there should be a provision to actually Create services as well as applications service is more Atomic or Singular in nature whereas an application can Bundle multiple services and it can provide a single graphical user interface So it means that the OSC has to now incorporate the Service creation and provisioning not only for services, but also applications Then these services and applications have to be Provided to the user in terms of deploying it on the customer premises equipment or the handheld device then some kind of Trial testing user experience has to be offered then Then once a user has used it then it has to be Removed from the user repository. So it means that this the process has to be carried out end to end Let's look at some protocols. This is just a very brief View on the kind of protocols which can be used in the engine architecture within the scope of the open service environment The there is a protocol known as the UDDI that is universal Description discovery and integration protocol. This is actually used to allow a certain service to be registered with the OSC environment for service provisioning through the service and transport strata Then we have the WSDL WSDL is basically a Description language that describes like XML schema the attributes the features the limitations and other details for the end user to make a choice Then whenever a service is to be offered then the service is to be managed effectively So there is something known as the Web service distribution management Framework and protocols now these wisdom protocols and services allow the end user to subscribe to these web services through the incorporation of Hyperlink or URL or a URI so it means that a UDDI WSDL wisdom are just Some of the protocols which can be used. It's not the end. There are other protocols and suites as well