anima-wg/autonomic-control-plane

Drafts and other work related primarily to the autonomic control plane

autonomic-control-plane's Issues

Discrepancy with RPL profile document

Section 6.11.1.12-14

These sections do not match up with the template entries I see in
draft-ietf-roll-applicability-template-09; can you explain the discrepancy?

TBD: I think these where details usually not covered by the RPL profile
but that we felt necessary to add for the case of the ACP.

definition of native interface

Loopback interfaces also exist without config, so the definition for "native interface" is not correct.

Make SRV.est example use HTTPS

On Tue, Jul 16, 2019 at 12:58:20PM -0400, Michael Richardson wrote:

I suggest that EST servers are never on port 80, and are likely
on port 443, or another port.

6.1.4.1. GRASP objective for EST server

ACP nodes that are EST servers MUST announce their service via GRASP
in the ACP through M_FLOOD messages. See [I-D.ietf-anima-grasp],
section 2.8.11 for the definition of this message type:

    Example:

    [M_FLOOD, 12340815, h'fd89b714f3db0000200000064000001', 210000,
           ["SRV.est", 4, 255 ],
           [O_IPv6_LOCATOR,
                h'fd89b714f3db0000200000064000001',
                TCP, 80]
    ]

                  Figure 3: GRASP SRV.est example

draft-ietf-anima-autonomic-control-plane-07 changes

Dealing with multiple certs/rfc822 addresses

Waiting for feedback from Cert experts to know what option will work,
then add text to ACP detailing dealing with multiple ULA addresses.

At minimum: device must create local address for every ACP address element in every certificate it has ... unless the device implements future work functions that use additional information to override this behavior.

draft-ietf-anima-stable-connectivity-03 changes