NFD » ndn-cxx

Need to update https://redmine.named-data.net/projects/nfd/wiki/FaceMgmt#FaceUri with the new syntax

Actually, I'm not sure if this is the correct design.

The syntax ether://[3c:15:c2:b8:b1:7e%25en0] was modeled after the link-local syntax proposed in #1428. However the semantics in the two cases are completely different. In the link-local address case, the interface name is used to disambiguate the address, because the address has link scope, so another link may have the same address. But both the address part and the interface name part refer to the same endpoint. Here instead the proposed syntax is abusing the scope identifier to represent two endpoints (remote and local) in a single FaceUri.

I think the way to go is to finally support a LocalUri field in faces/create management requests (see also #3471). That is, assuming we want to expose unicast ethernet face creation through the management protocol. With LocalUri+RemoteUri in faces/create, we don't need any additional FaceUri syntax, because existing ether:// and dev:// schemes already cover all use cases.

I kind of agree in principle, but if we going to get blocked by this for another half a year, I very much disagree.

If we proceed with localUri in create, who will work on this and can we make it work within a week?