• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Adaptation of RFC 1149 for IPv6

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    Adaptation of RFC 1149 for IPv6

    With the general adoption of IPv6 on the horizon the IETF have released an updated version of rfc1149 to address the requirements for IPv6.

    RFC 6214 - Adaptation of RFC 1149 for IPv6

    The original version of rfc 1149 can be found here for reference.

    http://tools.ietf.org/html/rfc1149
    Last edited by DaveB; 1 April 2011, 12:27.
    "Being nice costs nothing and sometimes gets you extra bacon" - Pondlife.

    #2
    Nice one Dave.

    Bit too geeky for many I suspect.
    Behold the warranty -- the bold print giveth and the fine print taketh away.

    Comment


      #3
      Interesting. Presumably IPv6 RFC1149 carriers would be able to use tunnels and bridges to seamlessly integrate with their IPv4 counterparts?
      Will work inside IR35. Or for food.

      Comment


        #4
        Originally posted by VectraMan View Post
        Interesting. Presumably IPv6 RFC1149 carriers would be able to use tunnels and bridges to seamlessly integrate with their IPv4 counterparts?
        This is addressed in the new RFC as below.

        Routing and Tunneling Considerations

        Routing carriers through the territory of similar carriers, without
        peering agreements, will sometimes cause abrupt route changes,
        looping packets, and out-of-order delivery. Similarly, routing
        carriers through the territory of predatory carriers may potentially
        cause severe packet loss. It is strongly recommended that these
        factors be considered in the routing algorithm used to create carrier
        routing tables. Implementers should consider policy-based routing to
        ensure reliable packet delivery by routing around areas where
        territorial and predatory carriers are prevalent.

        There is evidence that some carriers have a propensity to eat other
        carriers and then carry the eaten payloads. Perhaps this provides a
        new way to tunnel an IPv4 packet in an IPv6 payload, or vice versa.
        However, the decapsulation mechanism is unclear at the time of this
        writing.
        "Being nice costs nothing and sometimes gets you extra bacon" - Pondlife.

        Comment

        Working...
        X