1 / 9

Using RSVPv1 as NTLP (NSIS Transport Layer Protocol): suggestions for modifications on RFC2205

Using RSVPv1 as NTLP (NSIS Transport Layer Protocol): suggestions for modifications on RFC2205. Georgios.Karagiannis@eln.ericsson.se. Why this presentation?. why use RSVPv1 as NTLP? present a concept that uses RSVPv1 (RFC2205) as NTLP elicit feedback from the WG!. Why use RSVPv1 as NTLP.

unity-beard
Download Presentation

Using RSVPv1 as NTLP (NSIS Transport Layer Protocol): suggestions for modifications on RFC2205

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. Using RSVPv1 as NTLP (NSIS Transport Layer Protocol): suggestions for modifications on RFC2205 • Georgios.Karagiannis@eln.ericsson.se

  2. Why this presentation? • why use RSVPv1 as NTLP? • present a concept that uses RSVPv1 (RFC2205) as NTLP • elicit feedback from the WG!

  3. Why use RSVPv1 as NTLP • do not reinvent transport protocol features but use existing ones • shorten the time needed to standardize NTLP by reusing the current RSVP design experience and RSVP protocol specification • fulfil the flexibility and modularity requirement by: • allowing to certain scenarios to use, below NTLP, IETF existing protocols e.g., TCP, SCTP • the two level architecture concept: • new features have to be supported by NSLPs

  4. Proposed NTLP features (1) • support of Path-Coupled (Path-Directed) • soft state support • adaptation to load sharing • exchange local information between NSIS Forwarders located within one single administrative domain • any NSIS Forwarder is able to asynchronously generate a signaling message in case of unexpected situations • transports application layer (NSLP) "objects" that are opaque to NTLP

  5. Proposed NTLP features (2) • provides transparent operation through routers that do not support it • supports both IPv4 and IPv6

  6. Proposed concept (1) • NTLP protocol can be used for End-to-End, Edge-to-Edge, and End-to-Edge scenarios • separation in two main protocol levels, transport (NTLP) and application (NSLP) • proposed NTLP uses: • typically, stateful NSIS Initiators (NI), NSIS Responder (NR), NSIS Forwarder (NF) • stateful = NTLP aware node that maintains a NTLP transport layer state • when processing optimization is required, the NF interior (of an administrative domain) nodes can be NTLP stateless nodes • stateless = NTLP aware node that does not maintain a NTLP transport layer state

  7. Proposed concept (2)

  8. Proposed concept (3)

  9. Discussion • Is the presented concept acceptable to the WG?

More Related