buglwIP - A Lightweight TCP/IP stack - Bugs: bug #50264, Nomenclature: v4/v6 mapped...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #50264: Nomenclature: v4/v6 mapped addresses (low priority!)

Submitter:  David van Moolenbroek <dcvmoole>
Submitted:  Thu 09 Feb 2017 01:39:53 PM UTC
   
 
Category:  IPv6 Severity:  3 - Normal
Item Group:  Change Request Status:  Fixed
Privacy:  Public Assigned to:  None
Open/Closed:  Closed Planned Release:  None
lwIP version:  git head

Thu 09 Feb 2017 08:03:15 PM UTC, comment #1: 

Correct, David! Thanks for reporting!

Dirk Ziegelmeier <dziegel>
Group administrator
Thu 09 Feb 2017 01:39:53 PM UTC, original submission:  

I hate to bring this up, but right now it's probably still early enough to change without breaking much. The lwIP code consistently uses the term "IPv6-mapped IPv4 addresses" (and similar) for what are, in fact, "IPv4-mapped IPv6 addresses", as per RFC 4291 and others. This small mixup is present both in comments and in the form of macros such as ip6_addr_isipv6mappedipv4 and ip4_to_ipv6_mapped_ipv4. I think it'd be best to stick to the RFC term.

"git grep -i 'v6.*mapped'" finds most if not all occurrences.

FWIW I have to say that the naming also confuses me - it wasn't until after several uses of one of those macros that I realized that something was off at all. This is going to sound stupid, but whenever I need to think of the right order, it helps to realize that these addresses are all IPv6 addresses, just, of the "IPv4-mapped" type.

David van Moolenbroek <dcvmoole>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by dziegel (Posted a comment)
  • -email is unavailable- added by dcvmoole (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-02-09 dziegel StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code