NSIS-ka
A free C++ implementation of NSIS protocols

Opened 8 years ago

Last modified 8 years ago

#145 new defect

QoS-NSLP doesn't properly handle endpoints that are not QoS-NSLP aware

Reported by: stud-lenk Owned by: bless
Priority: major Milestone:
Component: QOS-NSLP Version:
Keywords: Cc:

Description

Given the following setting:

  • the usual testbed setup with the three nodes tb1, tb2 and tb3, interconnected like this:
       [ tb1 ]----[ tb2 ]----[ tb3 ]
    
  • QoS-NSLP is started on tb1 and tb2
  • GIST is started on tb3 without running QoS-NSLP

Now, when you try to establish a sender-initiated reservation starting on tb1 and targeted at tb3, the QoS-NSLP on tb2 ignores the GIST-Error returned from tb3 in reply to the initial GIST-Query. tb2 simply tries again and again to peer with tb3 by sending just another GIST-Query again and again.

Change History (1)

comment:1 Changed 8 years ago by stud-lenk

Right now the QoS-NSLP doesn't know about the error because GIST doesn't tell anything about it. See ticket #146.

Note: See TracTickets for help on using tickets.