Re: [Softwires] I-D Action: draft-ietf-softwire-map-12.txt

["Leaf Yeh" <[e-mail]>]

I am aware your reply just now, and was back to work yesterday from Chinese Lunar New Year holiday.

Ole - no, it is e.g. the /56 delegated to the end-user.

I got it.

Leaf > #4. In sec.6,
> “  The PSID field is left-padded to create a
>    16 bit field.  For an IPv4 prefix or a complete IPv4 address, the
>    PSID field is zero.”
> Q. Does the about ‘zero’ means the value of the PSID=0x 00, or the length of the PSID is zero? I guess it means the former, right?
Ole - correct.

I prefer we could replace the above 'zero' to be 'all 0s'.

Leaf > I think BR does not need to use the above IID. I prefer to replace the word ‘MAP node’ to be ‘MAP CE’. Right?
Ole - correct, but that leads us back to the discussion if the BR should be part of the MAP domain or not. that is should it be possible to reach an address of the BR using IPv4. that's why it says MAP node instead of MAP CE.

Sec.6 is named as "The IPv6 Interface Identifier". BR is not necessary to be reachable through IPv4, thought 'MAP node' sounds not wrong. 


Leaf > #7. In sec. 11
> “     They cannot
>       exist with MAP because each BRs checks that the IPv6 source
>       address of a received IPv6 packet is a CE address based on
>       Forwarding Mapping Rule. ”
> I think BRs check that the IPv6 source address of a received IPv6 packet is a CE address based on Basic Mapping Rule, and check that the IPv6 destination address of a received IPv6 packet is a CE address based on Forwarding Mapping Rule, right?
Ole -no, the destination IPv6 address is the BR address, and there is no point checking that.

Right, but my point was 'each BR (note that we don't need 's' here.) checks that whether the IPv6 source address of a received IPv6 packet is a CE address based on Basic Mapping Rule, not Forwarding Mapping Rule.', right?


Best Regards,
Leaf



-----Original Message-----
From: Ole Troan [mailto:[e-mail]] 
Sent: Friday, February 20, 2015 6:41 PM
To: Leaf Yeh
Cc: Suresh Krishnan; Ted Lemon; [e-mail]
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-12.txt

Leaf,

> I got a late read on this draft, and may find some editorial nits:
> 
> #1. In sec. 3,
>    "  End-user IPv6 prefix:   The IPv6 prefix assigned to an End-user CE by
>                            other means than MAP itself.  E.g.,
>                            Provisioned using DHCPv6 PD [RFC3633],
>                            assigned via SLAAC [RFC4862], or configured
>                            manually.  It is unique for each CE. "
> 
> Q. Does the above means ' End-user IPv6 prefix ' includes 's bits' (the subnet ID) in Fig.3?

no, it is e.g. the /56 delegated to the end-user.

> But in sec. 5.2,
> "  The MAP IPv6 address is created by concatenating the End-user IPv6
>    prefix with the MAP subnet identifier (if the End-user IPv6 prefix is
>    shorter than 64 bits) and the interface identifier as specified in
>    Section 6.  "
> 
> Q. Does the above means ' End-user IPv6 prefix ' does not include 's bits' (the subnet ID) in Fig.3? I guess we could include 's bits' (the subnet ID= MAP subnet identifier) into ' End-user IPv6 prefix '.

correct, the subnet-id is not included in the End-user IPv6 prefix.
the End-User IPv6 prefix is the "name" for the address block that the ISP gives to the subscriber.

> And in sec. 6,
> "  If the End-user IPv6 prefix length is larger than 64, the most
>    significant parts of the interface identifier is overwritten by the
>    prefix.  "
> 
> Q. Does the above means ' End-user IPv6 prefix ' includes 's bits' (the subnet ID) in Fig.3?

still not.

> #2. In sec. 5.1,
> "     For 'a' > 0, A MUST be
>       larger than 0.  This ensures that the algorithm excludes the
>       system ports.  For the default value of a (6), the system ports,
>       are excluded by requiring that A be greater than 0.  Smaller
>       values of a excludes a larger initial range.  E.g., a = 4, will
>       exclude ports 0 - 4095.  The interval between initiaL port numbers
>       of successive contiguous ranges assigned to the same user is
>       2^(16-a).   "
> 
> I prefer the above sentence could be
> "     For 'a' > 0, 'A' MUST be
>       larger than 0.  This ensures that the algorithm excludes the
>       system ports.  Smaller
>       values of 'a' excludes a larger initial range; e.g. 'a' = 4, will
>       exclude ports 0 - 4095.  The interval between initial port numbers
>       of successive contiguous ranges assigned to the same user is
>       2^(16-a).   "

I agree that we should tag 'a'. I'll add that.

> #3. In Fig.7 of sec. 5.3,
> “                   +----------+         +------------+
>                    |IPv4  sufx|         |Port-Set ID |
>                    +----------+         +------------+  ”
> I prefer the above ‘sufx’ could to be ‘suffix’.

ack.


> 
> #4. In sec.6,
> “  The PSID field is left-padded to create a
>    16 bit field.  For an IPv4 prefix or a complete IPv4 address, the
>    PSID field is zero.”
> 
> Q. Does the about ‘zero’ means the value of the PSID=0x 00, or the length of the PSID is zero? I guess it means the former, right?

correct.

> #5. In Fig.8 of sec.6,
> “The Interface identifier format of a MAP node is described below.
>   |          128-n-o-s bits          |
>    | 16 bits|    32 bits     | 16 bits|
>    +--------+----------------+--------+
>    |   0    |  IPv4 address  |  PSID  |
>    +--------+----+-----------+--------+  ”
> 
> I think BR does not need to use the above IID. I prefer to replace the word ‘MAP node’ to be ‘MAP CE’. Right?

correct, but that leads us back to the discussion if the BR should be part of the MAP domain or not. that is should it be possible to reach an address of the BR using IPv4. that's why it says MAP node instead of MAP CE.

> The above format looks like ‘128-n-o-s =64, but that is not always true. I prefer the IID format of MAP CE could be:
>   |          128-n-o-s bits          |
>    | <=16 bits|    32 bits     | 16 bits|
>    +--------+----------------+--------+
>    |   all 0s    |  IPv4 address  |  PSID  |
>    +--------+----+-----------+--------+  ”

whenever we speak about an IPv6 Internet ID it is 64 bits long. I'd rather not that we change that here.
I do see what you are saying though.

> #6. In sec. 8.1,
> “  Secondly, the node extracts the source IPv4
>    address and port from the IPv4 packet embedded inside the IPv6
>    packet.  If they are found to be outside the acceptable range, the
>    packet MUST be silently discard and a counter incremented to indicate
>    that a potential spoofing attack may be underway.”
> 
> I guess the better to substitute the above word ‘embedded’ could be ‘encapsulated’, right?

yes, thanks.

> 
> #7. In sec. 11
> “     They cannot
>       exist with MAP because each BRs checks that the IPv6 source
>       address of a received IPv6 packet is a CE address based on
>       Forwarding Mapping Rule. ”
> 
> I think BRs check that the IPv6 source address of a received IPv6 packet is a CE address based on Basic Mapping Rule, and check that the IPv6 destination address of a received IPv6 packet is a CE address based on Forwarding Mapping Rule, right?

no, the destination IPv6 address is the BR address, and there is no point checking that.

cheers,
Ole