[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[RAM] Re: I-D ACTION:draft-lear-lisp-nerd-01.txt

Hi Eliot,

I guess the RAM list is the place for this. I really only
have two comments at the moment.

> 3.1.  NERD Record Format

I don't think it's OK only to document the IPv4 format.
By the time any of this becomes reality we'll be in real need of
IPv6 support. It's much better to design it in now, and include
it in the calculations.

I think it "only" doubles your EID and RLOC sizes - 64 bits should
do fine; even a /64 mask seems unlikely in practice.

> 8.  Deployment Issues
>
>    While LISP and NERD are intended as experiments at this point, it is
>    already obvious one must give serious consideration to circular
>    dependencies with regard to the protocols used and the elements
>    within them.

Indeed one must. I strongly suggest getting rid of your dependency
on DNS for NERD bootstrapping and update. I see no way to assert
with certainty that http://www.example.com/eiddb/ can be resolved without
any indirect dependency on LISP - whereas http://192.0.2.123/eiddb/
or http://[2001:DB8::1234]/eiddb/ could be, by assigning server addresses
that are in fact global RLOCs. Also, this way you remove any security
issues associated with DNS, and any confusion about IPv4 vs IPv6
connectivity to the servers.

Since the NERD sevrvers will be just as crucial to the network as
the DNS TLD servers, I don't see a strong argument against managing
their IP addresses in much the same way as the TLD servers'.

   Brian

_______________________________________________
RAM mailing list
RAM at iab.org
https://www1.ietf.org/mailman/listinfo/ram