jagomart
digital resources
picture1_Ipv6 Ppt 76904 | Homenet Interim Principles Update


 179x       Filetype PPTX       File size 0.07 MB       Source: trac.ietf.org


File: Ipv6 Ppt 76904 | Homenet Interim Principles Update
update from discussions has been useful for feedback on the architecture principles some interesting discussions e g homenet versions security borders prefix configuration methods draft chown homenet arch 00 on ...

icon picture PPTX Filetype Power Point PPTX | Posted on 02 Sep 2022 | 3 years ago
Partial capture of text on file.
            Update from discussions
    • Has been useful for feedback on the 
      architecture principles
    • Some interesting discussions, e.g.
       –Homenet “versions”
       –Security borders
       –Prefix configuration methods
                        draft-chown-homenet-arch-00
         On re-use of existing protocols
    • Desirable to reuse existing protocols
    • Conservative approach
        –Give some weight to running code
        –But new capabilities are required
        –Need to know new protocols will be implemented
           • Some depends on open source development
    • Backwards compatibility
        –But don’t be concerned about existing broken 
          deployments (e.g. /64 due to CPE limitations)
                           draft-chown-homenet-arch-00
             On Topology Assumptions
     • No built-in assumptions
        –Make the least assumptions possible
     • Users want simple plug and play of devices
        –But what about arbitrary topologies/loops?
        –Enough to say do not introduce new IPv6 cases that 
          would break with IPv4+NAT?
     • Do we include multi-homing?
        –     nd
          Is 2  ISP for resilience unrealistic to consider?
        –Is work valid without multi-homed scenario?
                             draft-chown-homenet-arch-00
                       On dual-stack
     • Assume one of two cases
        –Dual-stack IPv4-IPv6, or IPv6 only
     • IPv6 solutions must not adversely affect IPv4
     • Seek to keep IPv4 and IPv6 topologies congruent 
       where possible
        –But with largest possible subnets
     • Specific transition tools out of scope
        –Though IPv6-only homenet may need to reach 
          external IPv4 content
                           draft-chown-homenet-arch-00
              Largest possible subnets
     • IPv4 home network deployments are most 
       commonly single subnet
        –Initial IPv6 deployments probably the same
     • Seek to use largest possible subnets
        –Route in IPv6 where IPv4 NAT is used
     • There are chained IPv4 NATs out there
        –e.g. VMs like Parallels, ICS, etc
        –Will we need IPv6 routed versions of these?
                            draft-chown-homenet-arch-00
The words contained in this file might help you see if this file matches what you are looking for:

...Update from discussions has been useful for feedback on the architecture principles some interesting e g homenet versions security borders prefix configuration methods draft chown arch re use of existing protocols desirable to reuse conservative approach give weight running code but new capabilities are required need know will be implemented depends open source development backwards compatibility don t concerned about broken deployments due cpe limitations topology assumptions no built in make least possible users want simple plug and play devices what arbitrary topologies loops enough say do not introduce ipv cases that would break with nat we include multi homing nd is isp resilience unrealistic consider work valid without homed scenario dual stack assume one two or only solutions must adversely affect seek keep congruent where largest subnets specific transition tools out scope though may reach external content home network most commonly single subnet initial probably same route use...

no reviews yet
Please Login to review.