Hello experts, While going through piggyback map rec handling at sec 6.1.3 of RFC6830
<snip> An ITR that is configured with mapping database information (i.e., it is also an ETR) MAY optionally include those mappings in a Map-Request. When an ETR configured to accept and verify such "piggybacked" mapping data receives such a Map-Request and it does not have this mapping in the map-cache, it MAY originate a "verifying Map-Request", addressed to the map-requesting ITR and the ETR MAY add a Map-Cache entry. If the ETR has a Map-Cache entry that matches the "piggybacked" EID and the RLOC is in the Locator-Set for the entry, then it may send the "verifying Map-Request" directly to the originating Map-Request source. If the RLOC is not in the Locator-Set, then the ETR MUST send the "verifying Map-Request" to the "piggybacked" EID. Doing this forces the "verifying Map-Request" to go through the mapping database system to reach the authoritative source of information about that EID, guarding against RLOC-spoofing in the "piggybacked" mapping data. </snip> I find it describes three scenarios when ETR gets the piggybacked Map records. 1) it does not have this mapping in the map-cache originate a "verifying Map-Request", addressed to the map-requesting ITR Question: would the verifying Map-Request sent to the "piggybacked" EID or directly to the ITRs using the one of RLOC in the Map records? It seems to me we need use EID, as this this is essentially the same as case 3) below. 2) On "If the ETR has a Map-Cache entry that matches the "piggybacked" EID and the RLOC is in the Locator-Set for the entry, then it may send the "verifying Map-Request" directly to the originating Map-Request source. " 3) On "If the RLOC is not in the Locator-Set, then the ETR MUST send the "verifying Map-Request" to the "piggybacked" EID." Question: for all the case 1),2),3), do we need to set the "A" bit for the "verifying Map-Request" to avoid RLOC-spoofing? It seems to me we need do it for case 1) and 3), but not necessary for case 2) Thanks Regards, -Rockson
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
