Re: [Anima] I-D Action: draft-nmdt-anima-management-bootstrap-00.txt

2017-07-12 Thread Brian E Carpenter
Hi, A few comments on this too. Again, it is a good topic to explore. 1. What's the relationship to draft-ietf-anima-stable-connectivity? 2. I am a bit confused by section 5.1. There is no such GRASP message as M_NEG_SYN. Are you proposing a negotiation objective or a synchronization objective?

Re: [Anima] I-D Action: draft-rfmesh-anima-iot-management-00.txt

2017-07-12 Thread Brian E Carpenter
Hi, A quick comment since I will not be in Prague. This draft opens an important topic. At least we should explore it in more depth. One comment is that specifying how GRASP unicast messages would work over UDP is not quite simple - that's why it isn't covered in the main GRASP spec. Ensuring tha

Re: [Anima] Is this how BRSKI/IPIP works?

2017-07-12 Thread Brian E Carpenter
OK, I'm getting there. More in line: On 13/07/2017 03:57, Michael Richardson wrote: > > Brian E Carpenter wrote: > >> Brian E Carpenter wrote: > Is the > >> following correct? > >> > >> > Topology (ASCII art): > >> > >> Topology is essentially correct. As you point out,

Re: [Anima] Is this how BRSKI/IPIP works?

2017-07-12 Thread Michael Richardson
Brian E Carpenter wrote: >> Brian E Carpenter wrote: > Is the >> following correct? >> >> > Topology (ASCII art): >> >> Topology is essentially correct. As you point out, RFC7217 is the >> recommendation going forward, so having a a big IEEE OUI allocation >> isn