In your previous mail you wrote:

   As I said at the meeting, I agree with the idea.
   
   Some isssues:
        - need to define the mapping between scope and top 4 bit?
                my guess is yes.  MIB peaple may want to map a value
                into alias (e.g. "link") from a remote system.
   
=> multicast scope values?

        - should care existing implementations?
                yes.  But I guess most of such applications use a interface
                index for scope_id, so it can be saved either:
            - assign scope value (4bit) 0 to link-local.
                or
            - implementation MAY accept the value 0 in implementation-
              specific manner, but SHOULD NOT return 0 for scope (4bit).
   
=> the MAY is fine.

        - need to introduce new functions to map scope-name and the value?
                I hope not to define new functions, so want to _define_
                the textual representation (e.g. "link", "site", ...)
                instead.
   
=> I prefer real names than xxxNNN. Can we get both (i.e. a config file
plus a default translation rule)?

Regards

[EMAIL PROTECTED]

PS: scopes are according to draft-ietf-ipngwg-addr-arch-v3-06.txt:
             0  reserved
             1  interface-local scope
             2  link-local scope
             3  subnet-local scope
             4  admin-local scope
             5  site-local scope
             6  (unassigned)
             7  (unassigned)
             8  organization-local scope
             9  (unassigned)
             A  (unassigned)
             B  (unassigned)
             C  (unassigned)
             D  (unassigned)
             E  global scope
             F  reserved
2 and 5 have a meaning for unicast.
--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to