1 / 4

NTLP strawman draft-schulzrinne-gimps

NTLP strawman draft-schulzrinne-gimps. Henning Schulzrinne Columbia University. Philosophy/approach. "Tool kit" approach: allow different NSLPs to choose trade-offs as needed: from unreliable one-shot to reliable large-message delivery allow NEs to choose time vs. space trade-off

joshuacalvin
Télécharger la présentation

NTLP strawman draft-schulzrinne-gimps

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. NTLP strawmandraft-schulzrinne-gimps Henning Schulzrinne Columbia University IETF57 - NSIS

  2. Philosophy/approach • "Tool kit" approach: • allow different NSLPs to choose trade-offs as needed: • from unreliable one-shot to reliable large-message delivery • allow NEs to choose time vs. space trade-off • RSVP-like in philosophy: • follow data path (but logically separable) • soft state state time-out, with explicit state removal • Transport philosophy: • do easy parts within simple transport: • small messages (< 500 bytes)  no fragmentation • first messages in session (unknown next hop) • reliable hop-by-hop delivery • leave hard parts to real transport protocols: • invoked only when needed • offer fast recovery (< n*RTT), flow control, congestion control, fragmentation, … IETF57 - NSIS

  3. Other design choices • TLV structure like RSVP • Refresh reduction like 2961 (needs details) • No explicit support for multicast • but addable – strict hop-by-hop behavior should make this easy IETF57 - NSIS

  4. What needs work • Name  • State maintenance for transport state: • remove when last session state removed • remove after idle timer (trade space for time) • remove LRU when out of space • State estimate (~ sessions + next hops) • Describe NSLP-specific next-hop selection • Packet format • Multihoming • NAT behavior • Mobility behavior • primarily dead-branch removal • Security mechanisms • can negotiate TLS and IPsec • how much is really needed IETF57 - NSIS

More Related