1. IETF 61 – Washington D.C.1 Detecting Network Attachment Best Current Practices draft-narayanan-dna-bcp-01.txt Sathya Narayanan Panasonic Greg Daley Monash Nicolas Montavont LSIIT-ULP

2. IETF 61 – Washington D.C.2 Approach Top-down approach We have been trying to get the structure of the document done. What are the different issues/things we want to present in the BCP? More work is needed on the text in each of the sections.

3. IETF 61 – Washington D.C.3 Organization Background & Motivation DNA Steps Validation of current configuration Reachability detection Additional information Security

4. IETF 61 – Washington D.C.4 DNA Steps Validation of current configuration Existing IPv6 configuration? By presence on particular link. Valid addresses and routers supported in the link. Reachability detection Reachability with current default router is crucial to continuing use of current configuration

5. IETF 61 – Washington D.C.5 Validation of current configuration Link change and router discovery Impact of router discovery procedure on link change decision CPL Complete prefix list – referring to CPL draft Router advertisement timers Different timers used in the RD procedure and their effect

6. IETF 61 – Washington D.C.6 Reachability detection Neighbor solicitation versus Router solicitation Use them in parallel? Authorization to use the router SEND routing certificates.

7. IETF 61 – Washington D.C.7 Additional information DNA Initiation (Hints) Current practices for hosts Current practices for routers Analysis of ECS and LCS Complications with DNA

8. IETF 61 – Washington D.C.8 Changes since –00 Complete re-organization Main focus of DNA in the first half (up to section 6) and additional information in the second half (from section 7 to 11). Structure within sections 5 & 6. Diff available at http://www.ctie.monash.edu.au/dna/draft-narayanan-dna-bcp-01-from-0.diff.html

9. IETF 61 – Washington D.C.9 Feedback received Insufficient treatment of verifying validity of current prefix. (previously Insufficient treatment of checking for link change ;-) ) Reachability confirmation and DAD out of scope I wish BCP draft to be more focused. These three comments stay as-is from last meeting Our focus was in re-organizing.

10. IETF 61 – Washington D.C.10 Discussion points Scope of BCP? Merge BCP and CPL?

11. IETF 61 – Washington D.C.11 Action plan Focus on IP prefix verification in section 5.1 Issues/difficulties How to avoid/reduce these issues/difficulties? Justification and requirement for reachability detection Additional cost in doing RD?

12. IETF 61 – Washington D.C.12 Action plan (Contd). Focus on sections 4 (DNA Steps), 5 (Validation of current configuration) & 6 (Reachability Detection). Publish –02 – End of November Further clarifications on 4,5 & 6 Focus on section 7 (DNA hints) & 12 (Security) Publish next version – End of January 05 Focus on sections 8 (CP for hosts), 9 (CP for routers), 10 (Analysis) and 11 (Complications) Before deadline for IETF62

13. IETF 61 – Washington D.C.13 Anything to be added/removed? Questions? Comments?