/
V6OPS WG – IETF #85 V6OPS WG – IETF #85

V6OPS WG – IETF #85 - PowerPoint Presentation

myesha-ticknor
myesha-ticknor . @myesha-ticknor
Follow
389 views
Uploaded On 2016-10-10

V6OPS WG – IETF #85 - PPT Presentation

IPv6 for 3GPP Cellular Hosts draftkorhonenv6opsrfc3316bis00 Jouni Korhonen Jari Arkko Teemu Savolainen Suresh Krishnan Outline Motivation for RFC 3316bis What has been changed Removed from RFC 3316 ID: 473748

3gpp rfc ipv6 addition rfc 3gpp addition ipv6 3316 changed text requirements 3316bis release specific clarifications recommendations removed v6ops

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "V6OPS WG – IETF #85" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

V6OPS WG – IETF #85IPv6 for 3GPP Cellular Hosts

draft-korhonen-v6ops-rfc3316bis-00

Jouni Korhonen

, Jari Arkko,

Teemu Savolainen, Suresh Krishnan Slide2

OutlineMotivation for RFC 3316bis

What has been changed

Removed from RFC 3316

Clarifications on the existing text

New additions to RFC 3316

Next stepsSlide3

Motivation for RFC 3316bisRFC 3316 was done ~9 years ago, prior IPv6 Node Requirements; No need to repeat RFC 6434 (was RFC 4294) Node Requirements content.

Reflect recent 3GPP developments and experience.

Some IPv6 RFCs are not mandated by 3GPP but make sense e.g., in hosts with multiple interfaces.

Keep it simple and conservative. This is not a 3GPP document or a tool for driving deployment specific requirements!Slide4

What has been changed – removed partsRemoval of all sections that can be directly found from RFC 6434 and do not require specific attention in 3GPP system:

IPv6 “basics”, PMTUD, IKE/

IPsec

, default address selection to name few..Slide5

What has been changed – clarifications

Clarifications to 3GPP link model and how Neighbor Discovery works on it.

Previous text in RFC 3316 was sometimes misinterpreted..

And there have been too many broken cellular host implementations and too strict

GGSNs

.

Already documented in RFC 6459 – endorsed here.

Clarification on the primary 3GPP IPv6 transition mechanism..

..which still is dual-stack. The rest are up to specific deployments.

Made the PPP IPV6CP support text conditional.Slide6

What has been changed – new additions

Addition of 3GPP EPS text i.e., Release-8 and onwards.

Addition of RFC 4191 (router preferences) recommendations.

Addition of DHCPv6-based Prefix Delegation recommendations, which is new to 3GPP Release-10.

Addition of RFC 6106 (RDNSS) recommendations.

Addition of RFC 5555 (DSMIPv6) regarding client based mobility, which is new to 3GPP Release-8.

Addition of Router Advertisement MTU option handling.

Addition of RFC 5095 that deprecates the RH0.

Addition of RFC 5722 and draft-ietf-6man-nd-extension-headers regarding the IPv6 fragmentation handling.

Addition of RFC 6583 for Neighbor Discovery denial-of-service attack considerations.Slide7

Next steps

Is there interest working on RFC 3316bis?

Adopt as a working group document..?