HyPath draft-cordeiro-nsis-hypath-00.txt

1
HyPathdraft-cordeiro-nsis-hypath-00.txt

• L. Cordeiro, M. Curado, E. Monteiro
• University of Coimbra, Portugal
• and
• F. Racaru, M. Diaz, C. Chassot
• LAAS-CNRS, France

2
Agenda

• Introduction
• Motivation
• HyPath Proposal
• Conclusion

3
Introduction

• This proposal is being developed in the European
  research project EuQoS (http//www.euqos.org)
• The project is composed by 24 partners
• The key objective of EuQoS is to research,
  develop, integrate, test, validate, trial and
  demonstrate
• end-to-end QoS
• technologies to support advanced QoS aware
  applications - voice, video-conferencing, video
  streaming, tele-engineering and medical
  applications - over multiple, heterogeneous
  research, scientific industrial and national
  research network infrastructure testbeds.

4
EuQoS partners

• 5 Network Providers (Prime Contractor is
  Telefonica)
• 5 Corporations
• 5 SMEs
• Consultants
• Small development companies
• 9 Research Institutes

5
Motivation (1/2)

• New QoS requirements
• Different treatments for IP packets
• Multi-domain Internet
• Inside one domain (AS) a central entity is in
  charge of QoS Management Resource Manager (RM)

6
Motivation (2/2)

• The motivation for the HyPath proposal is the
  need for a solution to the off-path signaling
  when the requirements are
• Network signaling must occur between the source
  and destination user domains
• Specific entities in the domains (resource
  managers) need to be signaled
• This entities may not be in the data path between
  the two users
• The users cannot be responsible for the network
  signaling
• The signaling must follow the same domains as the
  data (the same inter domain links should be used)

7
Notation

• NSIS domain domain with NSIS in all border
  routers
• Non-NSIS domain one or more border router
  without NSIS

8
HyPath proposal

• The source user interacts with its local entity
  through SIP or any other way to initiate the
  network signaling
• Use NSIS protocol to make the network signaling
  (QoS or other)
• Perform off-path signaling to signal the resource
  manager entity in each domain

9
First problem

• The off-path NSIS approach is not enough
• The signaling starts from the first RM and must
  follow the same domains as the data path

10
Proposal NSIS domains

• Use the domain routing protocol to discover the
  local egress border router of the data path
• Start the NSIS signaling from the egress border
  router and not from the local RM

11
Second problem

• What happens to domains without NSIS border
  routers?
• Which domains were not signaled?

12
Proposal non-NSIS domains

• If the next domain has no NSIS border routers,
  the NSIS messages cannot be intercepted, so the
  RM cannot be signaled
• Use the domain routing protocol to discover the
  local egress border router of the data path
• Inquire the egress border router to retrieve the
  next domain ingress border router information for
  the specific data path
• Send the message directly to the next domain RM
  IP address

13
Third problem

• Can we solve the two problems at the same time?
• NSIS off-path signaling starting at the egress
  border router
• Signal all domains, even if they are non-NSIS
  domains
• Is there a Hybrid solution?

14
HyPath Proposal (1/2)

• Use the inter-domain SLAs to share additional
  information between the domains
• Domain is an NSIS domain or not
• If not, share also the RM IP address
• In non-NSIS domains always send the message
  directly to the next RM
• In NSIS domains, before sending the signaling
  message, check if the next domain is a NSIS
  domain or not
• If its a NSIS domain send the message to the
  local ingress border router
• If its a non-NSIS domain send the message
  directly to the next RM

15
HyPath Proposal (2/2)

• A NSIS domain, when receiving a message from a
  non-NSIS domain
• If the next domain is a NSIS domain, the message
  is sent to the local ingress border router (info
  in the received message)
• If the next domain is a non-NSIS domain the
  message is sent directly to the next RM

16
Conclusions

• A RM entity where all adjacent domains are NSIS
  domains does not need to query the routing
  protocol (except for the first domain)
• Less complexity, better performance
• We hope that this is the future P
• Need the development of external functions to
  query the several routing protocols
• HyPath should be independent of the routing
  protocol (use a solution based on external
  functions)

17
Open issues

• Different routing for signaling messages
• Ex. qBGP
• Scalability issues
• NSIS domains solution
• non-NSIS domains solution
• Hybrid solution
• RM scalability is out of scope
• Security issues