transport selector

[Jason Cross <[e-mail]>]

Had a few questions in regards to how Quipu maps/uses the transport 
selectors in relation to the OSI and TCP stack.  The first question
is what does quipu do/use for a TSEL when using TCP when the
presentation address is declared as:

   Internet=192.xx.xx.xx+17003

I realize that 17003 is the port listened to, but this does not explain
the behavior witnessed (and decribed below).

The second question is why does quipu require a TSEL for OSI and not 
TCP? (actually, dish is the one that chokes without it) 

The reason I ask is that, recently, we configured our system to operate 
over both the OSI stack (we did a TLI port) and the TCP stack.  
I configured the presentation address for ros.quipu as:

   '025c'H/NS+47xxxxxxxxxxxxxxxxxxxxxx|Internet=192.xx.xx.xx+17003

When testing with dish for the OSI stack, I used the following in
dsaptailor:

   dsa_address mydsaname      '025c'H/NS+47xxxxxxxxxxxxxxxxxxxxxxxxxxx

and for TCP I used:

   dsa_address mydsaname      Internet=192.xx.xx.xx+17003

The test for the OSI stack was successful, but unsuccessful for TCP
until I added:

   dsa_address mydsaname      '025c'H/Internet=192.xx.xx.xx+17003

I assume in this case, that '025c'H is considered a TSEL.  Bad
assumption?

Thanks in advance.

ciao,
Jason Cross
EDS
Troy, Mi.