diff --git a/draft-ymbk-idr-l3nd.xml b/draft-ymbk-idr-l3nd.xml index c98b5a5..625845c 100644 --- a/draft-ymbk-idr-l3nd.xml +++ b/draft-ymbk-idr-l3nd.xml @@ -11,7 +11,7 @@ - + @@ -115,22 +115,35 @@ provides a similar solution at Layer-3, attempting to be as similar as reasonable to L3DL. + Some guiding principles when dealing with datacenters with tens + of thousands of devices are + + Predictable Reliability, + Security: Authorization and Integrity more than + Confidentiality, and + Massive Scalability + + + Layer-3 Neighbor Discovery (L3ND) provides brutally simple mechanisms for neighboring devices to + Discover each other's IP Addresses, Discover mutually supported layer-3 encapsulations, e.g. IP/MPLS, Discover Layer-3 IP and/or MPLS addressing of interfaces of the encapsulations, - Provide for authenticity and verification of protocol - messages. + Provide authenticity, integrity, and verification of protocol + messages, and + Accommodate scaling needed for EVPN etc. + L3DN is intended for use within single IP subnets (IP over Ethernet or other point-to-point or multi-point IP link) in order to exchange the data needed to bootstrap BGP-based peering, EVPN, etc.; - often in a datacenter Clos environment. Once - IP connectivity has been leveraged to discover1 layer-3 + especially in a datacenter Clos environment. + Once IP connectivity has been leveraged to discover1 layer-3 addressability and forwarding capabilities, normal IP forwarding and routing can take over.