AD fixes requested

[suehares]

1. List of AFI/SAFIs in draft – yes
2. Specify the VPN-ID for IP SEC in VPNs (for example - L3VPN (RD, prefix) uses RD) – Yes
3. Improve security section – Yes
4. Scaling issues – Not a concern for John
5. RTC was a concern for security - John brought this up.
6. Client routes only use Encapsulation Extended Community (Encaps-EC)
7. Clarity in writing - yes

[suehares]

AD comments addressed (John Scudder)

1. List of AFI/SAFI in draft for client routes - section 5 - paragraph 1. for underlay routes - section 6.1

2. VPN-ID See section 5.4 (client routes) and section 5.5 (data plane)

3. Improve security - rewritten To focus the security section, the error handling + manageability sections have been rewritten.

4. Scaling issues The scaling of the Underlay NLRI is a non-issue withy John since this use of BGP is a limited use.

5. RTC issues Section 4 was re-written to remove RTC concepts. Instead, the walled garden is created by configuring policy on the RR and the PE engaged in creating SDWAN Tunnel.

6. Client routes - Encapsulation Extended Community (Encaps-EC) versus TEA

Section 3.3 rewritten to clearly indicate just Encaps-EC is needed. Sections 5.1 (Encaps-Ec) and Section 5.2 (TEA) indicate there are two ways to specify a tunnel.

7. Re-organization of the document The document was re-organized in version 13.