>NI_NUMERICSCOPE is confusing. The draft does not mention
>NI_WITHSCOPEID. Earlier implementations of getnameinfo contain
>reference to NI_WITHSCOPEID which specifies that scope is to be
>returned. If NI_WITHSCOPEID is specified in flags then NI_NUMERICSCOPE
>makes sense. The scope is to be returned in numeric form. In the
>draft's current form, NI_NUMERICSCOPE seems to be a vestige,
>something that should have been removed but wasn't. At the moment
>IBM does not plan to include NI_NUMERICSCOPE in our implementation
>of getnameinfo. Comments on this interpretation of the draft would
>be appreciated.
NI_NUMERICSCOPE is introduced as there can be systems which use
symbolic representation for scopeid. for example, notations like
the following is acceptable:
fe80::1%loopback
fe80::1%ether0
in such case, you will want to selectively get numeric representation
in scopeid portion, or textual representation, depending on
NI_NUMERICSCOPE.
draft-ietf-ipngwg-scoping-arch-02.txt has more details on this topic.
>Further, can anyone elaborate on the meaning of NI_DGRAM. The draft does
>not provide an explanation of what this flag means. Again thanks for any
>comments.
with NI_DGRAM: getservbyname(foo, "udp")
without NI_DGRAM: getservbyname(foo, "tcp")
itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
