Re: 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
>>

stuff deleted

>>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?
>>

FROM Ton Verschuren - Network Development - SURFnet bv

>No, it's a TSEL!. Remember that the address IS an (OSI) Presentation
>>Address, only the lower layers are non-OSI, so you need a TSEL. For
>more info about the encoding of IP-addresses in presentation
>addresses, have a look at RFC1277:
>
>1277  PS   S. Kille, "Encoding Network Addresses to Support Operation Over 
>           Non-OSI Lower Layers", 11/27/1991. (Pages=10) (Format=.ps)         
>

I perused this rfc and am still wondering why, when using *only*
the TCP stack, I can get away with not specifying a TSEL (and what
Quipu uses as a default).  thanks again.

ciao,
Jason Cross
EDS
Troy, Mi.