Re: [Nsis-imp] Assigned numbers for version GIMPS -06

Hancock, Robert wrote:
>>My point was, to rely on NLI TLV to determine the size of PI (by 
>>minus other fields) may be simple but not efficient for processing.
> 
> from C.4.3 (the NLI format):
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   PI-Length   |    IP-TTL     |IP-Ver |        Reserved       |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    PI-Length = the byte length of the Peer-Identity field
>                (note that the Peer-Identity field itself is padded
>                to a whole number of words)
> 
> i'm not sure what encoding the PI as a separate object would buy you
> here.
Sorry, I have missed this field.

> but see for example the end of the second paragraph of 3.1,
> "If the routing state does not exist, it may be possible for GIMPS to
> send a message anyway, with the same encapsulation as used for a
> Query message."

Well, a GIMPS engine will always do whatever it is supposed to, as 
long as the task is part of the 'spec' and the implementation.

>>>- the RAO value of 0 is not realistic and in principle would
>>>  be NSLPID dependent. but exactly what the values should be
>>>  is a question for John's draft - or something like it ;-)
>>
>>That's what I also guessed but there was a question of being "0".
>>I like John's statement "An NSLPID must be associated with a unique 
>>RAO value." Assuming a preliminary one for basic testing would be 
>>needed, possibly using e.g., "diagnostics/ping/traceroute" function.
> 
> 
> yep - you'll find the same statement about NSLPIDs in the GIMPS draft,
> btw. but the point is, we can't allocate a 'real' ourselves (without
> going to IANA), so we just picked an easy one. Some IP stacks seem
> to have a problem with values other than 0, in our experience.
> 
Good to know of this. Any example platform?
Xiaoming

_______________________________________________
NSIS-imp mailing list
NSIS-imp@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/nsis-imp