 Baiklah. Terima kasih. Terima kasih, Roland. Jadi, selamat malam, semua. Terima kasih kerana menunjukkan. Ini adalah ketiga masa yang kita telah mencari sebuah sesuatu. Jadi nama saya Harish, Harish Pillay. Saya dari perspektif ISOC, saya bersama ISOC Singapura, Internet Society Singapura. Saya adalah Presiden Pasar Yaudah. Sekarang saya cuba melakukan sesuatu yang berkaitan dengan ITF. Interes dan peluang-peluang dan sebagainya di Singapura kerana ada sesuatu yang sangat baik yang kita dapat. Yang adalah mesyuarat ITF di Singapura pada November 2017. Jadi, untuk melakukan itu, ia baik untuk mempunyai orang di Singapura yang melakukan sesuatu dari prosesi ITF dan sebagainya. Jadi, itu sebabnya kita melakukan ini. Dan untuk... Anda boleh masuk. Jadi, apa yang kita cuba mencapai adalah mempunyai sebuah series di mana kita akan mempunyai, hari ini saya akan melakukan sedikit lebih terkenal kerana banyak lagi orang baru di luar. Tapi saya ada Cennam juga di sini yang telah mempunyai pengalaman dan membuat beberapa RFC-nya sebelumnya. Jadi, dia dapat berkongsi dengan kita beberapa nuancar di sebagainya dan sebagainya. Kita ada sebuah sesuatu yang akan datang hari ini, malam... Tidak, sebab hari ini bukan hari ini. Jadi, hari ini malam pada pejabat reda sebab tidak ada lagi. Tapi itu akan lebih seperti kerja untuk sebenarnya melalui apa yang Cennam akan bercakap tentang keputusan. Jadi, bagaimana saya memperbaiki RFC dan sebenarnya melakukan itu dan sebagainya. Dia akan beritahu apa yang kita cuba lakukan. Jadi, itu sebuah objektif untuk sesi hari ini. Jadi, dengan segala maksudnya, jika anda ada pertanyaan, bagaimana anda akan berhenti? Jadi, apa yang akan saya lakukan? Saya akan melakukannya sedikit lebih cepat sebab saya rasa saya ingin mempunyai masa dan sebagainya. Jadi, kita telah memperbaiki dan berkongsi bagaimana untuk menjadi champion IETF tetapi, ini sebenarnya sebuah keputusan. Itu yang kita cuba lakukan. Saya cuba keputusan dan keluar dengan banyak orang yang mungkin. Pertanyaan pertama di sini adalah, bagaimanakah anda pernah menulis RFC yang kita menulis oleh IETF? Dan bagaimanakah anda memahami apa yang anda menulis? Dan bagaimanakah anda memahami, memahami dan memperbaiki? Bagaimanakah anda memahami, memahami dan memperbaiki? Dan kami menulis. Dan kami menulis selepas menulis. Anda berkata, ini tidak akan berfungsi. Kenapa anda ingin menulis sesuatu? Saya tidak tahu. Atau menulis dan beritahu. Baiklah. Baiklah. Jadi, kita ada seseorang yang telah membuat beberapa perjalanan. Tapi perkara ini, ia boleh menjadi sebuah proses belajar jika anda tidak pernah melakukannya. Jadi, salah satu perkara yang kita cuba menulis dengan sesuatu ini adalah untuk pertama memperkenalkan siapa yang berminat. Dan anda melalui proses membuatnya. Dan kita akan mempunyai sesuatu mentos untuk membantu kami. Mentos akan berada di luar daripada di sebuah dunia. Jadi, memperkenalkan perjalanan kita atau perjalanan mereka atau sesuatu di antara. Dan memperkenalkan proses ini. Sekarang kita ada orang yang telah membuat sesuatu. Jadi, mereka juga boleh menjadi mentos untuk ini. Jadi, ia adalah perjalanan yang mereka cuba melakukan hari ini. Jadi, cepat-cepat saja. Bagaimana ITF? Ia adalah sebuah perjalanan yang membantu membuat internet cara ini hari ini. Jadi, jika anda mempunyai masalah dengan cara internet berlaku, ini adalah perjalanan yang anda mungkin mahu memperkenalkan. Tetapi, lebih penting, jangan hanya memperkenalkan, memperkenalkan perjalanan. Dan anda boleh memperkenalkan perjalanan. Semua jenis perjalanan lain di seluruh dunia tidak mempunyai peluang atau tidak memperkenalkan peluang untuk anda sebagai individu untuk memperkenalkan perjalanan. Perkenalkan bermaksud anda mempunyai modifikasi, mempunyai perjalanan baru, mempunyai pengalaman, mempunyai sesuatu dan sebenarnya memperkenalkan dan memperkenalkan, memperkenalkan dan memperkenalkan. Semua jenis perjalanan lain di seluruh dunia, termasuk seorang di Singapura, jenis perjalanan IT di Singapura, mereka semua mesti mempunyai sesuatu jenis peluang. Apabila saya katakan peluang, ia mesti mempunyai perjalanan kawasan kawasan kawasan atau perjalanan kawasan kawasan untuk anda, dan sementara itu, anda boleh memperkenalkan. Jika tidak, anda tidak memperkenalkan. IETF, bagaulah, memperkenalkan kepada semua kami. Untuk kita, anda mempunyai perjalanan kawasan, perjalanan, anda tidak mempunyai apa-apa, ia tidak penting, ia adalah tempat untuk bermula, dan kami memperkenalkan anda dan memperkenalkan anda dan memperkenalkan sesuatu untuk membuat perjalanan internet lebih baik. Jadi, ia adalah jenis perjalanan teknikal. Ia adalah jenis perjalanan. Ia bukan tempat yang anda datang dan mendengar berbicara. IETF itu tidak. Anda sebenarnya memperkenalkan perjalanan. Memperkenalkan kawasan, memperkenalkan speks, apa-apa yang perlu diperkenalkan. Okey, mari kita lihat. Jadi, membuat perjalanan internet lebih baik dengan membuat perjalanan tinggi, perjalanan teknikal. Ini sebenarnya perkara yang penting. Perjalanan teknikal. Mungkin, perjalanan yang sudah saya telah membuat sebelumnya di IETF. Ia tidak boleh menjadi perjalanan hari ini. Semua kita memperkenalkan dan, saya harap, masih memperkenalkan e-mail. Sekarang, perjalanan yang e-mail diperkenalkan dengan, ada banyak keputusan. Satu daripada mereka, ia dipanggil RFC 822. Tekniknya, ia diperkenalkan. Ada e-mail 822 yang memperkenalkan e-mail. Tapi, e-mail 822 masih ada. Ia ada sebuah nombor sekarang? Apa-apa pun yang nombor ada sekarang. Saya terus lupa nombor. Tapi, ia berkembang. Saya rasa, nombor standar sekarang dalam range 7000, range 7000 atau 8000, ada nombor yang ada sekarang. Jadi, nombor standar lama tak berlaku. Mereka tak berguna. Mereka hanya duduk di sana. Jadi, anda ada perkara historikal yang anda boleh lakukannya dan ia sangat menarik. Jadi, nombor standar ini adalah untuk membuat kekuatan yang baik, yang akan mempunyai cara orang memdesain, menggunakan dan memperkenalkan internet. Jadi, ia semua tentang internet. Jadi, jika anda rasa anda perlu memastikan internet berfungsi untuk anda dan sesiapa saja yang anda perlu memastikan. Ini tempat untuk bermula. Okey? Contribusi anda selalu selalu selamat datang. Jadi, beberapa perkara yang anda tahu jika anda tak pernah mengetahui apa yang internet berlaku seperti DNS, nama domain. Jika anda pernah mempunyai nama IP untuk pergi ke sesuatu tempat, itu sebab anda mungkin melakukannya pada masyarakat anda. Tetapi, apa-apa sistem lain, anda akan mempunyai nama dan anda akan mencari tempat yang anda mahu pergi ke. Jadi, semua orang menggunakan itu. Jadi, apa-apa yang kita mahu lakukannya? Kita mahu memastikan percayaan yang berlaku di internet. Jadi, banyak perkara yang masih berlaku tak berlaku atau tak berlaku dengan baik-baik. Mereka perlukan kerja yang lebih berlaku atau sesuatu seperti itu. Jadi, kemampuan, kemampuan, ini semua perkara yang kita perlu buat lebih banyak kerja. Jadi, ini tempat yang anda boleh memastikan sesuatu. Okey? ITF juga berlaku dengan organisasi lain yang berlaku dengan tempat ini, seperti W3C. Kami memiliki konsultasi web dunia swipe merah dunia bullish. Jadi, para orang-orang yang membuat kemampuan HTF untuk mencari bahan. Jadi, mereka memupuk. Jadi, mereka kan mengemas berita-tita. Jadi, mereka memposes săkut dan memastikan bentuk ITF yang boleh memalukan W3C. Jadi, terdapat dan tetap. Jadi, kita cuba menggemar. Ya, ITF tak pernah membuat video dan kodex. dan kenapa itu penting? Kerana banyak kodex yang anda perlu menggunakan untuk video dan audio dilengkapi oleh pakaian atau isu menggunakan dan sebagainya, itu menjadi suara Jadi, IETF menyebabkan dan membuat dua kodex, satu untuk audio dan satu untuk video dan saya rasa yang paling banyak untuk hari ini mempunyai ini Opus apakah ia disebut Opus? Opus kodex. Opus kodex, betul? Ia dari skib. Ia berubah dari skib. Jadi, perkara seperti itu. Jadi, ada keadaan yang dibuat untuk menerima beberapa masalah yang kita melakukan kerana kita perlukan. Pada akhirnya, internet berlaku kerana ia berlaku. Berlaku berlaku berlaku adalah anda harus mempunyai beberapa implementasi yang sama. Itu apabila ia berlaku. Jika ada seorang yang mempunyai, itu bukan berlaku berlaku. Ia hanya ialah implementasi dia. Jadi, berlaku berlaku adalah botong-bottongan sejujurnya. Jadi, perkara seperti itu, sangat penting untuk berlaku. Jadi, audio dan video. Dan sebenarnya, ini semua berlaku kerana web. Kerana anda melihat gambar yang saya mahu dengar. Ia MP3 atau apa yang ia? Dan anda perlu melalui net dengan kemungkinan yang tidak berlaku. Anda mahu... Jadi, mana yang anda perlukan? Apa yang berlaku dengan audio? Dan sepanjang banyak kerja. Ini sebenarnya sangat recent. Bila itu? Saya rasa 2-3 tahun lalu. Bagaimana dengan Oppos? Itu lebih dari 2 tahun lalu. Video adalah di sebuah cara kerana video adalah sebuah 5G. Ya, mereka menyebabkan itu dengan VPA. VPA adalah VPA. Kerana 5G ini menerima minit untuk anda. 5G ini menerima minit 729. Jadi, itu sebabnya... Jadi, ada banyak kemungkinan di sini. Ya. Okey. Jadi, apa yang anda katakan untuk membawa sebuah perkara yang lain? Bagaimana anda menyebabkan perkara yang lain? Ya. Dan perkara yang penting yang anda lakukannya, tetapi ia adalah perkara yang yang kita lakukannya. Ia MP3. Ia mempunyai tinggi yang tinggi. Anda boleh pergi untuk perkara yang sangat tinggi, tinggi kemungkinan yang tinggi, dan anda boleh menerima sekitar 6 atau 8 kW per sekitar. Atau cara yang tinggi untuk kemungkinan tinggi... Tidak, ini untuk radio ham. Saya minta anda menyebabkan perkara yang lain. Sudah tentu, anda akan menyebabkan perkara yang lain. Tidak, saya tidak menyebabkan perkara yang lain. Okey. Apa yang dikenalkan dalam membuat perkara yang penting untuk menyebabkan perkara yang penting? Sebaik hari yang saya mahu untuk menyebabkan perkara yang penting yang anda lakukannya. Kerana tak ada perkara yang penting. Saya minta anda menyebabkan perkara yang lain. Apakah perkara yang anda inginkan? Apa yang dikenalkan? Berapa lama anda akan menyebabkan perkara yang lain? Jadi jika anda telah buat perkara yang lain. Saya rasa saya hanya mengenai perkara. Kerana saya rasa mereka melakukan perkara yang lain. Sebelum sejak beberapa tahun itu mereka hanya membuat perkara yang lain untuk berkongsi apabila mereka boleh berkongsi. Ya. Ya. Sebelum saya akan mula menyebabkan perkara yang lain. Ya. Apa yang anda inginkan? Berkongsi. Pernah saya beritahu anda mungkin ada enam bulan sepanjang tahun. Ya. Baiklah. Sebaiknya, ia bermakna anda menyebabkan perkara yang anda inginkan. Makan kebanyakan keadaan yang menerimanya untuk mengeluarkan orang yang tidak terlalu berguna. Jika mereka tidak dapat mengeluarkan, maksud saya berjaya. Ya. So, assume that, right? So, yeah, it's six months to a year. It's probably what you need. And that's part of the design goals of IETS, so to speak. In the sense that you want to be making it quick. You don't want it to be languishing in committee after committee. No, it is working code. Ya, so I'm just sort of outside of the particular problems that E-mark had. And sort of, Emi said more broadly in, if I work in as a collaborator, we'll be couple guys who are building an open codec. Even low bit rate for the purpose. Ya, or specific purposes, why not? Ya, so it's primary and digital, but ya, it's a specific purpose low bit rate for its codec. So, I will probably guess something like this. If you start today, okay, if you craft up a draft, get it mentok by somebody just to make sure we cover the basis. You know, give it a week for that. Put it onto the mailing list, get people to start commenting on it. Maybe find a group, working group or working area, what do you call it? The area directors, one of the groups if necessary. Ya, so I agree. So there are ways, there are guides, so to speak, to help you find the right area to put it through. So you can go as quickly as the next ITF meeting, which is, when is it again? June, July in Berlin. We're talking about few months from now. Now, if you couldn't make it by then, the next one in November, which is in Seoul. So, you know, so I would say it can be quick. Ya, my concern is how to, but typically if you want to start something like that, typically the first meeting, you'll call it a bird of a feather. Ya, above. At the first meeting, usually. Ya, ya, so that's sort of the other half of the problem. The, this area in particular, is so over, paint plan, so colour tune is nice. Okay. One area where there is a, we give them a potential pattern, it's kind of work for that group, that's published, and they're in that group. So, the point is, I think, for the purpose of what we want to do, we will come to that. There are issues that we need to address as part of the standards making process. Ya, but the difficulty is, it's currently a small collaboration. Okay. It makes sense, it makes sense when you've got reps of half of the company and they're saying, yes, speaking of half of my employer, it's what we want to do. What happens when you've got really few and half of the employees with a working company who you'd like to, get a little tender for it, is that easy? I don't see why not. I don't see why not at all. I mean, the usual questions will be asked. How can you, or how do you tell there are no issues behind it in terms of patterns or whatever, right? If you can point to some prior art that has been published, maybe that's sufficient. Just think like that. Ya, okay. Thank you. So, I'm sure you've seen things like WebRTC, WebRTC allows you to do without having to have plugins and so on to do communication, and that's a great way to do real-time stuff as well. So, there are a lot of work that has already been done, but that doesn't mean the job is finished. There is a lot more new things that needs to be looked at. Different areas that may have to be looked at, something, and especially in the IoT space, I don't know what needs to be done there, but there's something to be done there, I'm sure. So, the structure of participation is there's no voting or no membership, sorry, no membership per se to be a member, you're not a member of IETF. You are there because you are Mr. X or Mr. Y, and that's it. You are part of the community. The actual standards work takes place on mailing list. All the work is actually documented because it's on a mailing list. All the disagreements, agreements, voting, whatever is happens in the mailing list. And attendance and phase-to-phase to resolve what they call big issues. Sometimes very hard to address it by email. It's best to sit down together and sort this thing out. So, it's really the hairy or the fauny issues that needs to be addressed face-to-face. Not so much as a punch-up. You're not there to punch people up, but I see you, you see me, we have everybody understanding what the issue is and let's try and sort this one item or two item. That's about it because you have already agreed on 99% of everything else. So, it's the one or two thing that needs to be fixed. So, that's the phase-to-phase part. But even after that is done, it doesn't mean it is passed. There is still a process you go through it doesn't show up here where essentially you have to vote on it. And after the voting and voting is then all documented in the mailing list and then it becomes candidate to become internet draft standard. Voting in the sense that because it's not membership-driven but to vote for that particular thing you have to be people have to agree this is what it is. Let me see, what else you want to talk about here? So, there are 129-ish working groups because working groups come and go as things get interesting or things have to retire, yes? Ya. So, involvement and voting that involve basically the vote and then it's okay, right? Ya. So, one particular issue I see the actual issue would be what if a big company comes in and has their employees vote on a certain standard in a certain place? Sure. It can happen? Ya, it can happen. Of course. Assume it happens. So, what? So, what? The standard that's part of the my details for the nobody because only one company It will be it will surface very quickly that this is being gained. You can't hide these things for too long. So, don't worry about it. I mean, that's the beauty or something like this, right? You don't have to worry about it. It's fine. It's okay. It's okay. Alright? So, there are a bunch of different working groups and there are seven areas where there are interests that are being focused on for work. So, they are called areas and each area has got a person who is in charge of the area. It's called an area director. All of these people that heading up the working groups and area directors and so on they are not paid people. They are not paid to do the job. They are all volunteers. They have their own day jobs. Whatever it may be. I think the the people who are hired to and pay the salary is the chair or IETF chair and the secretary. I don't know how many people. I think maybe less than 10. That's it. Okay. Everybody is a volunteer. So, when you go and participate in IETF meeting you pay away there. So, you have to pay for going there, wherever it's being held and usually they have administrative cost to run to rent to place and so on. So, you therefore may end up paying an attendance fee like a ticket for the event. It's not because of anything else you have to cover the cost. Okay. That's up to you. That's up to you. That would be. There are quite a lot of them who are sponsored and paid for by the by the employers. Which is fine. I mean that's entirely up to them. In fact, the best part about it is companies like Cisco, Huawei and a lot of these companies they actually do send their engineers and pay for everything because they see the value in building the standards so that others can also interoperate with whatever products that they make. So, they do see the value in it. And that's fine. And that's the whole point about creating a standard. Okay. Let's see. Let me go quickly and let's go through let me see what do I want to talk about here. Okay. So, these are some of the areas. So, the first one, general area is supporting, updating, maintaining any existing standards that we have. This is really the big picture, the meta picture about whatever else is happening in ITF. There's a security applications in real time, operations and management. So, each of them there's a description of each of these areas. You can certainly look into each of these area and find the working groups that come under the different areas for different specific aspects about it. I mean, things like IPv6 or DNSsec. You know, there's still a lot of things needs to be done by all means, you know, explore and figure out what you would be interested in doing. Okay. There is a lot of in today's within ITF, the fact that a lot of the technologies that are being used are built on open source technologies. So, it is using open source ideas and it is in turn feeding back into the ITF process as well in terms of how do you make sure that when you create something it is interoperable because you built it on open source tools and, you know, the testing and so on. So, there's a lot of interesting collaboration that and crossover of ideas between the ITF way of working and how the open source model works. So, it's actually a very fertile area for that. Let's see, what else do we want to talk about here? Ya. So, I was mentioning the internet of things is where I think there's going to be a lot of new work that needs to happen. Low power transmitters, you know, battery power systems, how do I handle delays, you know, I'm sure you have heard of the IP networks for planets, so that, you know, if I send a packet from Earth by the time it reaches Mars and comes back, if I send a ping, you know, to Mars.com, not the chocolate company but the planet. Okay, it may take, you'll take me at least an hour and a half before the ping returns. So, how do I, so do I have real time? So, things like, so how do I define something that works interplanetary? So, there is a interplanetary internet as well. You know, there's a lot of interesting stuff and just solving real problems, some of it is very out there but because someone has thought about it, there are things along the way that you can actually do with today. Okay, so that'll be kind of interesting. Alright, let's see. Okay, security and privacy is a big thing now as thanks to Snowden and the stuff that he has been able to do, which I think is a great thing. I think what he did was good. Just like cryptography, making sure your data at rest is encrypted, making sure you know, you manage your keys, so key management and so on and so forth. So, I think there's a lot of new work that needs to happen as well and maybe refreshing of what has to be done before and updating it in today's context. Especially when you deal with IoT, how do I ensure you know, the traffic that is coming out of my sensors are actually secure? Do I care? And if I don't care, what does that mean? What am I exposed to? I might be exposed to anything. So, there are philosophical question that needs to be answered by the technology that is being implemented. So, it works in both ways. Alright. So, let's see. What I want to talk a little bit more is so they had a it's the first time they actually did this as a hackathon in Yokohama. This was, I think, was it last year? Yeah, yeah, last year. This was last year's ITF. ITF 94. So, they had a hackathon there. So, this is the phrase I go with, rough consensus and working code. So, if you propose something, right? So, Roland, you're proposing a particular codec. Let's get the code working. The actual code. So, it's rough consensus and running code. You know, you can go. There's nothing stopping you from going from working code and documenting the standard after that. Because you already know this works. Then let's now figure out and document it and that becomes the RFC. But that's how actually the whole entire thing seems to agree from everything. So, they had working systems. Now let's document the thing and work that way. So, you don't have to write first to implement it. Implement something and then you'll write it. And then you find, oops, why not? Okay. Let's see. Okay, this is just to explain the process in which the ITF work gets done. So, the first one it says tech development is done in the working group. So, if you pick Roland's idea about a codec, so what happens? So, you may have to identify a working group under one of the areas. Okay. But it can be an individual effort as well. So, you could be doing it all by yourself so, and then the proposal is published as a working document as it's called internet draft. The working document is revised and republish for discussion. All on the mailing list. Okay. There are no conference calls for these things. It's all on the mailing list. So, it's 24 hours a day. Okay. If you can handle the mail load, then the working document is submitted to standard group via the area directors and they do the review and then they would issue RFC number. Ya. So, the final step is when IES internet engineering standard group is satisfied that the document is sent to the RFC editor and you're given a number. New RFC number. And there you go. Now, you're a published RFC author. Okay. This entire process can take six months, can take a year, can take ten years. It depends on what needs to be done and whether there's anybody pushing it. Okay. So, there's no guarantee that you will succeed, but at least you will have a lot of scars along the way. Hopefully, not do painful scars, right? Actually, one of the example is like XMPP, right? Ya, XMPP, actually start by start off by actually start off that thing and then actually come to RFC 79. Okay. Instead of 223 or something like that. Alright. Now, with the rough consensus, what does that mean? It means it doesn't require unanimity. Everybody doesn't have to agree. What is interesting is the second one. There's no formal voting. That means I don't raise my hand to say, okay, how many say yes, how many say no. It is by humming. Alright, you want to hum? It's a very loud hum because there's a lot of people humming. That's kind of rough consensus. But it's the only one person humming. Ya, I know that's the only person who has agreed to. The rest have not agreed at all. So it is by humming. So why were some of the, why were some of these things added into the equation? Because there are some real human situations where it may become a problem because you may be sitting with your boss. At this meeting. At ITF face to face. And you know, your organization that you're representing may not be agreeable with what has been proposed. But you are agreeable. But your boss is not. So would you want your boss to know that you are agreeable? By raising your hand? So by not having to do that, you may have a gentle hum. Or may have a loud hum depending on how you did. So you kind of drown out in the hum. So that's what one use case for the hum. Your boss is next to you. So how do you manage that? So things like that. I mean these are small little human related problems that is being solved. Okay. By engineers. Engineers rule the world. Exactly. Alright. So and disputes are resolved by discussion or mailing list and face to face. So that's the purpose of the face to face meetings because you want to move things forward. And eventually final final final final decision is on the mailing list. So if it's not on the mailing list, it has not been decided. It's the equivalent of black and white. Alright. So everything is open. It's on plain text files. It's not in PDF. It's all ASCII text files. So if you go to rfc.org I think it is. You find all the rfc's are listed there from the very first one. Okay. Even very interesting ones. Okay. I don't know how many of you have heard of the AVN TCP? AVN TCP? AVIN TCP? You have. Have you implemented it? Aha. So AVN TCP is all about using pigeons to send the TCP packets. You tie the IP. Ya, I'm sorry. IPs. You tie the IP onto the legs of the pigeon or the back of the pigeon wherever you want to do it. That's up to you. And then let the pigeon go to where it's supposed to go to, deliver the packet and then come back. So it will be a little bit faster than going to the Mars and back. But hopefully the bird mix it back before it's shot down. Right? So AVN actually has been implemented somewhere. I was told somebody the New Zealand tried to do that or somewhere. Did an AVN TCP. High packet loss. Ya, very high packet loss. You're doing shooting season, right? So there are some silly ones but that's part of the fun. That's part of the fun. Let's see. What else? I think that's okay so over 7000 RFCs. I'm not sure what else I want to talk about here. Okay so maybe the scope where does IETF actually work in? IETF doesn't work in W3C space. That's what W3C does. IETF doesn't work at the electronic side of the game. You're not defining what is the circuit supposed to do. That's not what it's doing. There are standards already for some of the networking stuff like IEEE 802, Wi-Fi, Wired Networks. So that's done by IEEE. But they all effectively work together at some point. But those are the areas that IETF doesn't touch because somebody's already doing it. So in the last line it says generally hard to clarify and define the scope but where there is nobody doing it? Why not? Why not, right? I don't think anybody wants to do AVN TCP other than IETF. I have no idea who else wants to do AVN TCP. But anyway, that's the point about this. You kind of know where IETF should be. It's all about the internet. So where do I draw the line of the internet? Yes, it goes to the network card? No. Network card is somebody else. But slightly higher than network card. Where the wires? No. That is not even IETF. But the packets that go through that becomes interesting. That's where IETF will sit. Sometimes it's quite hard. It's just just a tiny layer just a tiny layer that's where you are and then you disappear. Alright. I think that's where I will stop because I want to give Chenan the time to go through a demo for I talk about stuff. I just want to say that IETF and ISO and all of these are known. There is a term called SDOs. Standards definition standard SDO stands for Standards Development Organisations. It's a global, it's a generic term. So anybody is a SDO. So IETF is an SDO. But each SDO has their own business model, so to speak. IETF doesn't have a business model in the sense that they don't make money. But things like Spring Singapore or ISO they have to generate cash because they have no other way to do it. So their business model is different. They are also a standard making organisation. Alright. I shall end here and hand off to Chenan so that we can talk about what we want to do from an outreach perspective and the next stage. So what do you need from me? Can you switch the... Okay, just one. I think just now you request for comment. I think this is to repeat what was just said. Because once it becomes a standard it's a request for comment. Most standards out there are something trying or something that actually play doesn't really do that. But when you go to ITG which is the whole entire world is doing that so deploy recommendations. I'm trying to do more interlating so it will destroy unfortunately, it's private. Just a quick introduction for myself. I'm an Aishapuri Aishapuri member Singapore Computer Charters. Coming from Aishapuri perspective I wrote some tenets for ITGF. Aishapuri You know, 2011 R Some ITGF standards. That's kind of my previous life. I did with some IoT voice while as STM. So I'm not going to do this for very long because I think it's kind of quite on Friday probably I'll cover some of the stuff such as reading some of the ITF standards out there. It can go a very wide range kind of stuff. So we will do something simple like basic encoding rule that's kind of the beginning to start off what all sorts of stuff because I think we need to start somewhere I'm trying to figure out where should we start somewhere to read the specs itself so we probably will start off with basic encoding rule the main reason for doing that is because with that we will accompany with a workshop that write a simple just a recipe kind of a thing from a point A to a point B using Python if time permits we probably because this is kind of when you do about sockets we start off with sockets anyway per grade university sockets in a very long term as time progress you may want to have if you want to do something more advanced things that what the things happen in between you probably want to do mini-net because what you do of course you can do IP layer but there's certain things you may want to use mini-net it's easier to do because oh yes okay mini-net is kind of it started off from Stanford University it is kind of a simulation tool for you to write protocols it started off from open flow people use it to test out switches virtual switch for you to run all kinds of protocols run on top whether it's IP, MPLS or IPv4, IPv6 various kind of protocols that you can test it on meaning it's a very small simulation tool that you can use Python to quote on an intensive packet across because sometimes you want to have a bigger network because what I'm going to do for workshop 3 is basically I just have to two VMs to run up it's you probably need a notebook with windows I mean right you start off with a virtual box and you install two VMs and then you try to write a support okay that's what I'm going to cover on this one we can cover other things Friday if you have every other time any question for me? alright so what do we need other than that I think there is the main thing that how much time do we need it takes about I was thinking about 2 hours 2 hours 2 hours 2 hours if we can go is there any other than the computers any other stuff that they need to load up on the machine maybe useful to state as well what's your box? what's your box? I mean actually I think so huh? so what so that you can what's your box is kind of something like that okay actually whatever here just inform there will just just load on it's a Linux machine that you're running in so if you're running Linux then you don't need windows yeah yeah it doesn't matter very important yeah it doesn't matter but most important thing is we need to load a few Linux machine okay how many are you using? so bottom line from my point of view if you're running a Linux machine you already have virtual to run a virtual machine so that's easy so it's a trivial job you don't need virtual box or anything like that so you just go for it but you need Python you need I need to run two Linux machines okay so you need two VMs at least two concurrently to be run while you're doing this thing so then you need Python and what else? that's all so Python and system capable of running virtual machines doesn't have to be windows doesn't have to be windows yeah just that perfect yeah any questions then for what we want to do on Friday Friday this is for Friday so this is the time where we want to actually yeah to try and achieve knowing creating you know reading the standards yeah what time is it? we want to well I won't fix the time but we can start at 7 o'clock 6.30 to 7 o'clock yeah this coming Friday which is the 13th the best day to do anything exactly that's when the best protocols get written right I mean some of the other things that I found on that so for example you talk about south to laurabit and it can only be fixed in the sentence so for that particular yeah is there an RFC in this one for this Oof 2.0? well it's an RFC but the thing is no one have fixed it this is about 2060 it's just our gen somewhere in germany so there you go now we are not cryptographers but we are going to try and fix the problem yeah once you fix the problem then you can contribute back to the standards itself because everyone have to use these right? yeah I know because of that so yeah yeah, there's some issues behind it yes yeah but the rest of the whole download is using this you know so but you know this is part of the fun so the objective on friday is for you to get your fingers and hands and your mind wet in something that you have not done before so we will guide you along the way we will make mistakes along the way and that's part of the fun so I reckon 2 hours maybe 3 hours and we will try and get pizza the promise of pizza on friday I think it's a fair thing and beer yeah the promise is allowed it's red hat anything goes it's not an alcohol-free zone okay so any questions there any questions or comments or areas of concern that you may have at all do you think it's interesting do you think we should even bother doing this except the camera lady has visited in pictures so if there are no comments and questions thank you very much for coming okay appreciate your time and effort there you go I can't oh that's not loud enough I already mentioned that so IETF 100 will be in Singapore in November next year and whether it's going to be held at Marina Bay or somewhere else but that's Swiss Hotel Swiss Hotel okay so the challenge with any IETF event our meeting is that it's about 1,000, 5,000, 2,000 people will come for that so there's a lot of although it's TBD by Singapore they haven't officially put it out there yet okay sorry yeah if you are in Singapore yes but it's good to sign up first but there may be fees involved in participating only because you're going to cover the cost that's the objective but we would have categories for students free and blah and there are fellowships there are fellowships that are granted by the Interest Society to attend so even for the ones that's coming up in it's closed already it's already done for souls it's closed already only one okay so I made a mistake I didn't introduce two very important people from the Interest Society Asia Pacific office in Singapore Amelia and Olivia so thank you very much for supporting us in doing this because she's there so be nice to her you may get an extra slice unencrypted unencrypted encrypted or unencrypted iRTF I don't know I don't know what their schedule is I haven't checked any of those things yet I mean they haven't put out Singapore yet although that is