updated ipv4 id specification n.
Download
Skip this Video
Download Presentation
Updated IPv4 ID Specification

Loading in 2 Seconds...

play fullscreen
1 / 7

Updated IPv4 ID Specification - PowerPoint PPT Presentation


  • 111 Views
  • Uploaded on

Updated IPv4 ID Specification. IETF 77 Joe Touch, USC/ISI. Quick review. Current hosts don’t ensure ID uniqueness within 2MSL Recognize existing practice Explicitly limit ID to fragmentation Align IPv4 and IPv6 ID and fragmentation. -03 / intarea mods. Issued as inarea doc Text mods

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Updated IPv4 ID Specification' - gavivi


Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
updated ipv4 id specification

Updated IPv4 ID Specification

IETF 77

Joe Touch, USC/ISI

quick review
Quick review
  • Current hosts don’t ensure ID uniqueness within 2MSL
    • Recognize existing practice
  • Explicitly limit ID to fragmentation
    • Align IPv4 and IPv6 ID and fragmentation
03 intarea mods
-03 / intarea mods
  • Issued as inarea doc
  • Text mods
    • Reformatted pseudocode fragments
    • Clarified requirements text
    • Mathis ack’d only
ipv4 vs ipv6 ids
IPv4 vs. IPv6 IDs

ID MSL uniqueness already ignored

summary of changes
Summary of changes
  • SHOULD limit fragmentation in IPv4
    • Only at source (DF=1)
    • Only where use is safe (ID unique or integrity check)
  • MUST NOT fragment if ID not unique
  • MUST NOT reuse ID if fragmented/ableMUST NOT use for duplicate detection
  • MUST ignore overlap fragments
    • Now possible only by net duplication as transient
remaining issues
Remaining issues
  • Clarify ‘maximum jitter’
    • “time during which reordering is expected & tolerated.”
  • Clarify IPv6 examples
    • IPv6 ID also in PTB ICMP, only for v6 talking to v4
    • May update RFC 2460 (?)
  • Clarify why overlaps are prohibited
    • Never retransmit with same ID
    • Now impacts only in-net replication (transient impact)
more issues
More issues
  • Impact on NATs
    • NATs act as hosts; SHOULD set DF, not fragment
  • Note that there are boxes that ignore DF
    • With predictable results ;-)
  • Transition plan
    • Do we need one? – it might help with ignore-DF case
    • When to cease?