1 / 12

IPv6 over IPv6CS: Issues from WG and IETF LC

This document addresses concerns regarding the transmission of IPv6 over different transport methods, such as IP.CS and Eth.CS, with focus on classification rules, secondary management connections, MTU recommendations, and service flow establishment in IPv6 networks. It discusses conflicting indications between base stations and access routers, dual-stack support, and outlines next steps for revision based on IETF LC feedback.

cmuller
Download Presentation

IPv6 over IPv6CS: Issues from WG and IETF LC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPv6 over IPv6CS: Issues from WG and IETF LC draft-ietf-16ng-ipv6-over-ipv6cs Basavaraj Patil 16NG WG meeting@IETF68

  2. IPv6 over IPCS or EthCS • With multiple ways of transporting IPv6, concern about interoperability and default mode was raised • Clarified that IPv6 over IP CS is the default method for IPv6 transmission over 802.16 • BS SHOULD support IP CS and Eth CS to ensure support for all host types IETF68

  3. Classification rules in IPCS • Mechanism and use of Classification rules in the CS and mapping to appropriate transport CID confusing • Clarified in Rev 8 the process of classification and the rules to map packets to a CID IETF68

  4. Use of Secondary mgmt connection • IEEE 802.16 defines the secondary management connection that can be used for address config etc. • Secondary management connection support is optional in .16e • Used in .16d(?) • For adress config or management? • I-D recommends the use of regular transport connection for configuration as well as user traffic • Add text clarifying the use of SMC in .16d (Pending change depending on clarification of use in .16d) IETF68

  5. MaxRtrAdvInterval • The I-D allows the RA interval to be between 4 secs and 21600 secs with default being 10800 secs • Changes the default recommendation in 2461bis for 802.16 links • Reason: Idle mode hosts, battery lifetime issues IETF68

  6. MTU recommendation • The 802.16 link can support an IP packet of MTU=2038 bytes • Default value recommendation in I-D = 1500 bytes (as per 2460) • Hosts may use PMTUD to determine the MTU • MTU option in RA can indicate the value to a host IETF68

  7. IPv4/v6 on the same transport connection • Question about running IPv4 and IPv6 over the same transport connection • Clarified that the transport connection established is specifically for IPv4, IPv6, 802.3,… • 802.16s IPCS design limits v4/v6 transmission on the same link • GPCS in the future will fix this issue IETF68

  8. Service flow establishment • Network trigger for service flow establishment vs Host requesting it; Which is the default option? • Default option: Host requesting service flow on successful authentication specified in Rev 8 IETF68

  9. Conflicting BS vs AR indications • The BS (in case of managed hosts) may indicate the use of SLAAC or DHCP to hosts for address config • This may be in conflict with the address config policy of the AR • Solution: Deployment/config issue to be noted in the I-D to ensure that both are aligned IETF68

  10. Dual-stack support • How does this specification support DS hosts? • It does not. The I-D is applicable only for IPv6 and a separate I-D will be specified for IPv4. Clarified scope. IETF68

  11. Next Steps • IETF LC ends Mar 31st • Revise I-D (09) if required in case of issues identified during the LC IETF68

  12. IETF68

More Related