draft-levy-idr-6pe-survey-00.txt Francois Le Faucheur - flefauch@cisco

1. 6PE (IPv6 over IPv4 MPLS) - Implementation Report draft-levy-idr-6pe-survey-00.txtFrancois Le Faucheur - flefauch@cisco.com Eric Levy-Abegnoli Francois Le Faucheur Cisco Systems Rajiv Papneja Isocore

2. 5 Responses to 6PE Implementation Survey • two router implementations: • - Cisco Systems • - Juniper Networks • three implementations on network test equipments: • - Ixia • - Agilent • - Spirent

3. Compliance Statements • MUSTs • All the implementations comply with all the “MUSTs" • SHOULDs/MAYs • Implementations on test equipment also supports all (or all but one) "SHOULDs"/"MAYs" • LABEL ALLOCATION STRATEGY: • Cisco implementation allocates and advertises an arbitrary label • Juniper implementation allocates IPv6 Explicit NULL label • Both implementation comply with the [6PE] “MUST” to accept both forms of advertisement • Both Implementations interoperate

4. Interop Testing • Basic interoperability between Cisco, Juniper and Ixia has been successfully tested as part of an ISOCORE interop event • See section 3 for details on scope of tests

5. Any Issues Identified? • No issues identified with 6PE spec • (like ambiguity, holes,..) • One point brought to light : • while case (b) of inter-AS operations is applicable when arbitrary labels are used, case (b) is not applicable in the case where IPv6 Explicit-Null is used • because in that case, it does not result in the use of inter-AS LSPs from ingress 6PE to egress 6PE allowing label switching at every hop including ASBRs. Rather, it results in IPv6 lookup and IPv6 forwarding at the ASBRs.

6. Next Steps • This was a necessary step to allow 6PE to move to RFC (as per Routing Area rules) • let that draft die its natural death