Stanford Seminar - Software-Defined Networking at the Crossroads

Поділитися
Вставка
  • Опубліковано 15 вер 2024

КОМЕНТАРІ • 34

  • @kenigiri
    @kenigiri 3 роки тому +2

    I absolutely love this professor! Insightful and engaging talk even after 8 years! I am sure it would have been awesome to be in Scott Shenker's classes.

  • @LuisAntolin
    @LuisAntolin 10 років тому +3

    Great talk. It is nice to hear about SDN from a clean non-vendor-specific perspective.
    Also, good job on clarifying and demystifying some of the more abstract concepts.
    Thanks for sharing!

  • @SumitArora1234
    @SumitArora1234 11 років тому

    The concept of SDN is very-very well explained, If you are the one who want to dive in SDN, then this video will add great value to your learning,concepts and provide you a clear thought process about SDN.

  • @sandraramirez7248
    @sandraramirez7248 2 роки тому

    Very valuable pictures like this are allowing to make and create the knowledge more flexible

  • @andreyagenosov3286
    @andreyagenosov3286 7 років тому

    Amazing talk! In a first 15 min it explains what SND is all about. It's interesting to watch it even after learning SDN technology during several months.

  • @PelczarTomasz
    @PelczarTomasz 10 років тому

    Let's Stanford ... My appreciation ... I am at the very end of quite basic task of counting from B-address of broadcast and maximum of host of the address started 172.16 plus mask of 22 bits ... Both broadcast and multicast are one of the most crucial during passing every kind of the computer science studies even on the worse higher schools focused on computing, during my high school I had learnt crontab after exam and later I had no problems to pass exams of UNIX administration at all, one mistake can learn the rest of another experiences and can score as the very good goal to prompt into the level of Bachelor of Art within the topic, which is applied of ... Very valuable pictures like this are allowing to make and create the knowledge more flexible, sustainable, optimal and higher within the level of being advanced in case of computer science ...

  • @nitinksri
    @nitinksri 11 років тому

    Gr8 preso if u want to understand the history of sdn, the network problems that needed to be solved, how they are broken up and each piece solved separately.

  • @gnazi1968
    @gnazi1968 10 років тому

    Very clear and simple explanation! good lecture

  • @victorescobar8620
    @victorescobar8620 10 років тому +4

    Great talk. However, the audio seems to be slightly distorted (feedback from the mic, perhaps?). If the audio could be smoothed out, it would make the video that much more pleasant to watch. :)

  • @bcbabloo
    @bcbabloo 11 років тому

    Very well explained and the best seminar on SDN :)

  • @aknewhope
    @aknewhope 10 років тому +2

    I agree completely. Software should be used to the edge which should be the end host. Core routers are implemented using hardware ASICs. Simple and makes sense.

  • @salonigandhi8567
    @salonigandhi8567 7 років тому

    great explanation on edge networks!

  • @yackawaytube
    @yackawaytube 8 років тому

    Very nice lecture. Little bit dated though. It would be nice to have another one

  • @johnstaup8313
    @johnstaup8313 10 років тому

    Good info, thank you very much! I'm actually looking for an SDN architect to join our team in Omaha. We handled 58 BILLION minutes last year and want to deploy an SDN strategy in the very short term. Any questions? Please ask!

  • @shanthoshparamasivam4887
    @shanthoshparamasivam4887 9 років тому +1

    Awesome lecture!! can i get the IEEE paper for this topic?

    • @romanvanickis5141
      @romanvanickis5141 8 років тому

      +shanthosh paramasivam arxiv.org/pdf/1406.0440.pdf

  • @KnightHawk1990
    @KnightHawk1990 9 років тому

    So how is the question posed with regards to middle-boxes and per packet processing really answered? I didn't quite get to hear a solid, definitive answer on that end with regards to how SDN would help solve the problem. The only thing mentioned was that better hardware implementation at the middle-boxes would help decrease the latency that the processing might cause. Can anyone please shed some light on this?

    • @invisiblesurfing
      @invisiblesurfing 8 років тому

      +Moeez R. I heard that we should split the MB processing in the edge.

    • @invisiblesurfing
      @invisiblesurfing 8 років тому

      +Moeez R. hi, i found a new paper of shenker, called Open Network Interfaces for Carrier Networks, hope it helps you

  • @jeffsicuranza1168
    @jeffsicuranza1168 9 років тому +2

    Not bad, but he should do one now 2 years later as an update for we are still in a crossroad.

    • @tctfone1
      @tctfone1 7 років тому

      well, we are still there

  • @dehand1037
    @dehand1037 8 років тому

    Hi Stanfordonline, where can I get the information about the SDN History? For example: Who created SDN? Where it created? When it created? The invention until 2016? I hope you can help me. Thank you.

    • @ejo5817
      @ejo5817 5 років тому

      www.cs.princeton.edu/courses/archive/fall13/cos597E/papers/sdnhistory.pdf

  • @rogernevez5187
    @rogernevez5187 8 років тому

    Anyone know a mailing list (or something similar) to exchange ideas about computer networks?

  • @adnanshafi1481
    @adnanshafi1481 8 років тому +3

    @35:03 "When a packet comes in wrong direction, I ll just remove a destination " What is that suppose to mean?

    • @abbassaied3281
      @abbassaied3281 6 років тому

      It will just drop the packets that goes from A to B.

    • @Leonew1234
      @Leonew1234 5 років тому

      He was talking about how a core router responds to link failure. So with SDN, and if the cord router senses a link failure and that core router is only forwarding packets, then to recover from that link failure the core router has only to remove the destination address at the end of that failed link from its forwarding table and that is all to it to recover from failure. So a packet coming in a wrong direction ( means going to a failed link) all that we need to do is to remove the wrong destination from the forwarding table. A task that could be done in nano seconds instead of hundreds of milliseconds.

  • @vamsikrishnaIIT
    @vamsikrishnaIIT 10 років тому

    best on SDN..

  • @srheal07
    @srheal07 6 років тому

    Martin cansado is not the inventor SDN absolutely wrong

  • @scottfranco1962
    @scottfranco1962 8 років тому

    Lets see, the ideal network has intelligence in the end nodes, and passes a simple label with the packets, and all the internal switches do is forward the packets without regard for what protocol is running, etc.
    Yea, its called ATM (Asyncronous transfer mode) and its been around for decades. MPLS was ripped off from ATM.

    • @srheal07
      @srheal07 8 років тому

      +Scott Franco Truth be told, and even martin admits its SDN was coined by academia, he is not the inventor and given him to much credit is not acceptable. Also there is no way they invented SDN.... I knew about SDN since 2007 in college my self at devry university

  • @MINECRAFTISLIFUE
    @MINECRAFTISLIFUE 3 місяці тому

    P/161130/01/2024/041332